Component burden impl committed

View: New views
17 Messages — Rating Filter:   Alert me  

Component burden impl committed

by hammett-2 :: Rate this Message:

| View Threaded | Show Only this Message


Still need to do some clean up, enable some more tests. Bleeding-edge
runners, please give windsor/mk a more careful evaluation. It might
misbehave. If it does, please report it asap.
Thanks

--
Cheers,
hammett
http://hammett.castleproject.org/

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Castle Project Development List" group.
To post to this group, send email to castle-project-devel@...
To unsubscribe from this group, send email to castle-project-devel+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en
-~----------~----~----~----~------~----~------~--~---


Re: Component burden impl committed

by Colin Ramsay-2 :: Rate this Message:

| View Threaded | Show Only this Message

My knowledge of the component burden problem is very limited, but I do feel that congratulations are in order Hammett!

On Tue, Oct 7, 2008 at 1:17 AM, hammett <hammett@...> wrote:

Still need to do some clean up, enable some more tests. Bleeding-edge
runners, please give windsor/mk a more careful evaluation. It might
misbehave. If it does, please report it asap.
Thanks

--
Cheers,
hammett
http://hammett.castleproject.org/




--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Castle Project Development List" group.
To post to this group, send email to castle-project-devel@...
To unsubscribe from this group, send email to castle-project-devel+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en
-~----------~----~----~----~------~----~------~--~---


Re: Component burden impl committed

by Tuna Toksoz :: Rate this Message:

| View Threaded | Show Only this Message

Cool! Does that mean that the release is too close?

On Tue, Oct 7, 2008 at 3:17 AM, hammett <hammett@...> wrote:

Still need to do some clean up, enable some more tests. Bleeding-edge
runners, please give windsor/mk a more careful evaluation. It might
misbehave. If it does, please report it asap.
Thanks

--
Cheers,
hammett
http://hammett.castleproject.org/





--
Tuna Toksöz

Typos included to enhance the readers attention!

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Castle Project Development List" group.
To post to this group, send email to castle-project-devel@...
To unsubscribe from this group, send email to castle-project-devel+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en
-~----------~----~----~----~------~----~------~--~---


Re: Component burden impl committed

by Craig Neuwirt :: Rate this Message:

| View Threaded | Show Only this Message

Cool Hammett,

  Looks nice!!

On Mon, Oct 6, 2008 at 7:17 PM, hammett <hammett@...> wrote:

Still need to do some clean up, enable some more tests. Bleeding-edge
runners, please give windsor/mk a more careful evaluation. It might
misbehave. If it does, please report it asap.
Thanks

--
Cheers,
hammett
http://hammett.castleproject.org/




--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Castle Project Development List" group.
To post to this group, send email to castle-project-devel@...
To unsubscribe from this group, send email to castle-project-devel+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en
-~----------~----~----~----~------~----~------~--~---


Re: Component burden impl committed

by hammett-2 :: Rate this Message:

| View Threaded | Show Only this Message


Gosh, I hope so.

On Tue, Oct 7, 2008 at 12:54 AM, Tuna Toksöz <tehlike@...> wrote:

> Cool! Does that mean that the release is too close?
>
> On Tue, Oct 7, 2008 at 3:17 AM, hammett <hammett@...> wrote:
>>
>> Still need to do some clean up, enable some more tests. Bleeding-edge
>> runners, please give windsor/mk a more careful evaluation. It might
>> misbehave. If it does, please report it asap.
>> Thanks
>>
>> --
>> Cheers,
>> hammett
>> http://hammett.castleproject.org/
>>
>>
>
>
>
> --
> Tuna Toksöz
>
> Typos included to enhance the readers attention!
>
> >
>



--
Cheers,
hammett
http://hammett.castleproject.org/

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Castle Project Development List" group.
To post to this group, send email to castle-project-devel@...
To unsubscribe from this group, send email to castle-project-devel+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en
-~----------~----~----~----~------~----~------~--~---


Re: Component burden impl committed

by hammett-2 :: Rate this Message:

| View Threaded | Show Only this Message


I've changed ccnet to invoke nant with -t:net-3.5 (or something like
that). Still failing. Any hints?



--
Cheers,
hammett
http://hammett.castleproject.org/

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Castle Project Development List" group.
To post to this group, send email to castle-project-devel@...
To unsubscribe from this group, send email to castle-project-devel+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en
-~----------~----~----~----~------~----~------~--~---


Re: Component burden impl committed

by Ayende Rahien-2 :: Rate this Message:

| View Threaded | Show Only this Message

Do we have ..net 3.5 on the server?

On Wed, Oct 8, 2008 at 5:30 PM, hammett <hammett@...> wrote:

I've changed ccnet to invoke nant with -t:net-3.5 (or something like
that). Still failing. Any hints?


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Castle Project Development List" group.
To post to this group, send email to castle-project-devel@...
To unsubscribe from this group, send email to castle-project-devel+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en
-~----------~----~----~----~------~----~------~--~---


Re: Component burden impl committed

by hammett-2 :: Rate this Message:

| View Threaded | Show Only this Message


Yes. donjon uses 3.5, and is built on the same build server.

On Wed, Oct 8, 2008 at 8:49 AM, Ayende Rahien <ayende@...> wrote:

> Do we have ..net 3.5 on the server?
>
> On Wed, Oct 8, 2008 at 5:30 PM, hammett <hammett@...> wrote:
>>
>> I've changed ccnet to invoke nant with -t:net-3.5 (or something like
>> that). Still failing. Any hints?
>>
>>
>>
>> --
>> Cheers,
>> hammett
>> http://hammett.castleproject.org/
>>
>>
>
>
> >
>



--
Cheers,
hammett
http://hammett.castleproject.org/

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Castle Project Development List" group.
To post to this group, send email to castle-project-devel@...
To unsubscribe from this group, send email to castle-project-devel+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en
-~----------~----~----~----~------~----~------~--~---


Re: Component burden impl committed

by Louis DeJardin :: Rate this Message:

| View Threaded | Show Only this Message


Cool. Is this change motivated by the IServiceLocator activity in some
way? This doesn't change the need to call ReleaseComponent on the
outermost objects that are resolved, does it?

On Oct 8, 5:21 pm, hammett <hamm...@...> wrote:

> Yes. donjon uses 3.5, and is built on the same build server.
>
>
>
> On Wed, Oct 8, 2008 at 8:49 AM, Ayende Rahien <aye...@...> wrote:
> > Do we have ..net 3.5 on the server?
>
> > On Wed, Oct 8, 2008 at 5:30 PM, hammett <hamm...@...> wrote:
>
> >> I've changed ccnet to invoke nant with -t:net-3.5 (or something like
> >> that). Still failing. Any hints?
>
> >> --
> >> Cheers,
> >> hammett
> >>http://hammett.castleproject.org/
>
> --
> Cheers,
> hammetthttp://hammett.castleproject.org/
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Castle Project Development List" group.
To post to this group, send email to castle-project-devel@...
To unsubscribe from this group, send email to castle-project-devel+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en
-~----------~----~----~----~------~----~------~--~---


Re: Component burden impl committed

by hammett-2 :: Rate this Message:

| View Threaded | Show Only this Message


The release needs to be invoked on the root component.

On Wed, Oct 8, 2008 at 4:32 PM, Louis DeJardin <Louis.DeJardin@...> wrote:

>
> Cool. Is this change motivated by the IServiceLocator activity in some
> way? This doesn't change the need to call ReleaseComponent on the
> outermost objects that are resolved, does it?
>
> On Oct 8, 5:21 pm, hammett <hamm...@...> wrote:
>> Yes. donjon uses 3.5, and is built on the same build server.
>>
>>
>>
>> On Wed, Oct 8, 2008 at 8:49 AM, Ayende Rahien <aye...@...> wrote:
>> > Do we have ..net 3.5 on the server?
>>
>> > On Wed, Oct 8, 2008 at 5:30 PM, hammett <hamm...@...> wrote:
>>
>> >> I've changed ccnet to invoke nant with -t:net-3.5 (or something like
>> >> that). Still failing. Any hints?
>>
>> >> --
>> >> Cheers,
>> >> hammett
>> >>http://hammett.castleproject.org/
>>
>> --
>> Cheers,
>> hammetthttp://hammett.castleproject.org/
> >
>



--
Cheers,
hammett
http://hammett.castleproject.org/

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Castle Project Development List" group.
To post to this group, send email to castle-project-devel@...
To unsubscribe from this group, send email to castle-project-devel+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en
-~----------~----~----~----~------~----~------~--~---


Re: Component burden impl committed

by Ayende Rahien-2 :: Rate this Message:

| View Threaded | Show Only this Message

all calls are ending up with release policy, which needs to do explicit thread management to handle that safely.
it also serialize all calls to the container that end up resolving an instance of an object.

I change the hashtable syncronization in the all component release policy to use RWL, but it still requires some thought

On Tue, Oct 7, 2008 at 2:17 AM, hammett <hammett@...> wrote:

Still need to do some clean up, enable some more tests. Bleeding-edge
runners, please give windsor/mk a more careful evaluation. It might
misbehave. If it does, please report it asap.
Thanks

--
Cheers,
hammett
http://hammett.castleproject.org/




--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Castle Project Development List" group.
To post to this group, send email to castle-project-devel@...
To unsubscribe from this group, send email to castle-project-devel+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en
-~----------~----~----~----~------~----~------~--~---


Re: Component burden impl committed

by hammett-2 :: Rate this Message:

| View Threaded | Show Only this Message


Use of ReadWriterLockSlim would be best.

On Thu, Oct 9, 2008 at 1:13 AM, Ayende Rahien <ayende@...> wrote:

> all calls are ending up with release policy, which needs to do explicit
> thread management to handle that safely.
> it also serialize all calls to the container that end up resolving an
> instance of an object.
>
> I change the hashtable syncronization in the all component release policy to
> use RWL, but it still requires some thought
>
> On Tue, Oct 7, 2008 at 2:17 AM, hammett <hammett@...> wrote:
>>
>> Still need to do some clean up, enable some more tests. Bleeding-edge
>> runners, please give windsor/mk a more careful evaluation. It might
>> misbehave. If it does, please report it asap.
>> Thanks
>>
>> --
>> Cheers,
>> hammett
>> http://hammett.castleproject.org/
>>
>>
>
>
> >
>



--
Cheers,
hammett
http://hammett.castleproject.org/

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Castle Project Development List" group.
To post to this group, send email to castle-project-devel@...
To unsubscribe from this group, send email to castle-project-devel+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en
-~----------~----~----~----~------~----~------~--~---


Re: Component burden impl committed

by Ayende Rahien-2 :: Rate this Message:

| View Threaded | Show Only this Message

Already committed that, but it still syncing all thread on this.
Since by default this is only for pooled components, I don't think it is too bad, though.

On Thu, Oct 9, 2008 at 5:01 PM, hammett <hammett@...> wrote:

Use of ReadWriterLockSlim would be best.

On Thu, Oct 9, 2008 at 1:13 AM, Ayende Rahien <ayende@...> wrote:
> all calls are ending up with release policy, which needs to do explicit
> thread management to handle that safely.
> it also serialize all calls to the container that end up resolving an
> instance of an object.
>
> I change the hashtable syncronization in the all component release policy to
> use RWL, but it still requires some thought
>
> On Tue, Oct 7, 2008 at 2:17 AM, hammett <hammett@...> wrote:
>>
>> Still need to do some clean up, enable some more tests. Bleeding-edge
>> runners, please give windsor/mk a more careful evaluation. It might
>> misbehave. If it does, please report it asap.
>> Thanks
>>
>> --
>> Cheers,
>> hammett
>> http://hammett.castleproject.org/
>>
>>
>
>
> >
>



--
Cheers,
hammett
http://hammett.castleproject.org/




--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Castle Project Development List" group.
To post to this group, send email to castle-project-devel@...
To unsubscribe from this group, send email to castle-project-devel+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en
-~----------~----~----~----~------~----~------~--~---


Re: Component burden impl committed

by hammett-2 :: Rate this Message:

| View Threaded | Show Only this Message


It's for all components with decommission lifecycle steps. I'll get
back to it next weekend.

On Thu, Oct 9, 2008 at 8:09 AM, Ayende Rahien <ayende@...> wrote:

> Already committed that, but it still syncing all thread on this.
> Since by default this is only for pooled components, I don't think it is too
> bad, though.
>
> On Thu, Oct 9, 2008 at 5:01 PM, hammett <hammett@...> wrote:
>>
>> Use of ReadWriterLockSlim would be best.
>>
>> On Thu, Oct 9, 2008 at 1:13 AM, Ayende Rahien <ayende@...> wrote:
>> > all calls are ending up with release policy, which needs to do explicit
>> > thread management to handle that safely.
>> > it also serialize all calls to the container that end up resolving an
>> > instance of an object.
>> >
>> > I change the hashtable syncronization in the all component release
>> > policy to
>> > use RWL, but it still requires some thought
>> >
>> > On Tue, Oct 7, 2008 at 2:17 AM, hammett <hammett@...> wrote:
>> >>
>> >> Still need to do some clean up, enable some more tests. Bleeding-edge
>> >> runners, please give windsor/mk a more careful evaluation. It might
>> >> misbehave. If it does, please report it asap.
>> >> Thanks
>> >>
>> >> --
>> >> Cheers,
>> >> hammett
>> >> http://hammett.castleproject.org/
>> >>
>> >>
>> >
>> >
>> > >
>> >
>>
>>
>>
>> --
>> Cheers,
>> hammett
>> http://hammett.castleproject.org/
>>
>>
>
>
> >
>



--
Cheers,
hammett
http://hammett.castleproject.org/

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Castle Project Development List" group.
To post to this group, send email to castle-project-devel@...
To unsubscribe from this group, send email to castle-project-devel+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en
-~----------~----~----~----~------~----~------~--~---


Re: Component burden impl committed

by Roelof Blom :: Rate this Message:

| View Threaded | Show Only this Message

From the build server's log:
[echo] Detected NAnt 0.86 Beta 1, consider upgrading to a newer version when building for .NET 3.5

Not sure if this is the problem but perhaps you should consider upgrading NAnt to a recent nightly from http://nant.sourceforge.net/nightly/

-- Roelof.

On Wed, Oct 8, 2008 at 5:30 PM, hammett <hammett@...> wrote:

I've changed ccnet to invoke nant with -t:net-3.5 (or something like
that). Still failing. Any hints?


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Castle Project Development List" group.
To post to this group, send email to castle-project-devel@...
To unsubscribe from this group, send email to castle-project-devel+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en
-~----------~----~----~----~------~----~------~--~---


Re: Component burden impl committed

by Ken Egozi :: Rate this Message:

| View Threaded | Show Only this Message

yeah I had to go for Beta2 nightly builds when I moved to 3.5


On Fri, Oct 10, 2008 at 9:40 AM, Roelof Blom <roelof.blom@...> wrote:
From the build server's log:
[echo] Detected NAnt 0.86 Beta 1, consider upgrading to a newer version when building for .NET 3.5

Not sure if this is the problem but perhaps you should consider upgrading NAnt to a recent nightly from http://nant.sourceforge.net/nightly/

-- Roelof.


On Wed, Oct 8, 2008 at 5:30 PM, hammett <hammett@...> wrote:

I've changed ccnet to invoke nant with -t:net-3.5 (or something like
that). Still failing. Any hints?






--
Ken Egozi.
http://www.kenegozi.com/blog
http://www.musicglue.com
http://www.castleproject.org
http://www.gotfriends.co.il

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Castle Project Development List" group.
To post to this group, send email to castle-project-devel@...
To unsubscribe from this group, send email to castle-project-devel+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en
-~----------~----~----~----~------~----~------~--~---


Re: Component burden impl committed

by hammett-2 :: Rate this Message:

| View Threaded | Show Only this Message


Ok, gonna fix that.

On Fri, Oct 10, 2008 at 12:40 AM, Roelof Blom <roelof.blom@...> wrote:

> From the build server's log:
> [echo] Detected NAnt 0.86 Beta 1, consider upgrading to a newer version when
> building for .NET 3.5
>
> Not sure if this is the problem but perhaps you should consider upgrading
> NAnt to a recent nightly from http://nant.sourceforge.net/nightly/
>
> -- Roelof.
>
> On Wed, Oct 8, 2008 at 5:30 PM, hammett <hammett@...> wrote:
>>
>> I've changed ccnet to invoke nant with -t:net-3.5 (or something like
>> that). Still failing. Any hints?
>>
>>
>>
>> --
>> Cheers,
>> hammett
>> http://hammett.castleproject.org/
>>
>>
>
>
> >
>



--
Cheers,
hammett
http://hammett.castleproject.org/

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Castle Project Development List" group.
To post to this group, send email to castle-project-devel@...
To unsubscribe from this group, send email to castle-project-devel+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en
-~----------~----~----~----~------~----~------~--~---