Re: BlockThread

2004-01-02 Thread Niclas Hedhman
On Saturday 03 January 2004 14:39, Niclas Hedhman wrote: > On Saturday 03 January 2004 13:49, Niclas Hedhman wrote: > > Argument in favour of doing 2. > > == > > So far I have only heard "people normally does;" > > It seems that a fair number of avalon-excalibur and aval

Re: BlockThread

2004-01-02 Thread Niclas Hedhman
On Saturday 03 January 2004 13:49, Niclas Hedhman wrote: > Argument in favour of doing 2. > == > So far I have only heard "people normally does;" It seems that a fair number of avalon-excalibur and avalon-components components are using the Thread.currentThread().getCo

Re: BlockThread

2004-01-02 Thread Niclas Hedhman
On Saturday 03 January 2004 07:36, Stephen McConnell wrote: > Niclas Hedhman wrote: > > This is _NOT GOOD_, I know that, and I think Steve knows it by now, and I > > will change it later for sure, > I'm buried deep in model listeners and notifiers and I'm unlikely to > even thing about the threa

Re: happy new year! -- s/2003/2004/

2004-01-02 Thread Niclas Hedhman
On Saturday 03 January 2004 08:13, Alexis Agahi wrote: > And here is my 2004 early contribution: > find . -name '*.java' -print | xargs perl -pi -e 's/2003/2004/g' Slightly dangerous. The Copyright law doesn't require us to change the date other than when we "make new Copyrighted additions/chang

Re: BlockThread

2004-01-02 Thread Niclas Hedhman
On Saturday 03 January 2004 04:43, Noel J. Bergman wrote: > Niclas Hedhman wrote: > > The rationale/intention behind this design is a bit flawed, but > > centers around assigning the Block Classloader to the Thread's > > ContextClassloader, but the intention is not fulfilled... > > Would the easies

Re: happy new year! -- s/2003/2004/

2004-01-02 Thread Alexis Agahi
On Saturday 03 January 2004 01:11, Stephen McConnell wrote: > Leo Simons wrote: > > a nice TODO: update all copyright statements to recognize we're now > > living in the brand-new 2004. Any takers? > Go for it Leo! > Cheers, Steve. Happy new year everybody! And here is my 2004 early contribution

Re: happy new year! -- s/2003/2004/

2004-01-02 Thread Stephen McConnell
Leo Simons wrote: a nice TODO: update all copyright statements to recognize we're now living in the brand-new 2004. Any takers? Go for it Leo! Cheers, Steve. -- || | Magic by Merlin| | Production by Avalon

Re: BlockThread

2004-01-02 Thread Stephen McConnell
Niclas Hedhman wrote: On Friday 02 January 2004 22:59, Fernando Padilla wrote: Is there any reason why a new Thread is created and then kept around doing and endless sleep loop ( sleeping for measely 300 millisec ), for every block instanciation? This is _NOT GOOD_, I know that, and I think Stev

happy new year! -- s/2003/2004/

2004-01-02 Thread Leo Simons
a nice TODO: update all copyright statements to recognize we're now living in the brand-new 2004. Any takers? cheers! - Leo PS: this was so easy when we still used ant's :/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For ad

Re: [merlin] update and bug fix

2004-01-02 Thread Jörg Schaible
Hi Steve, Stephen McConnell wrote: > Based on feedback re. scripts on different unix platforms everything > seems to be ready to go. The one outstanding point of validation > concerns a Cygwin test. If anyone is running Merlin under this > environment - confirmation would be appreciated. Also,

RE: BlockThread

2004-01-02 Thread Noel J. Bergman
Niclas Hedhman wrote: > The rationale/intention behind this design is a bit flawed, but > centers around assigning the Block Classloader to the Thread's > ContextClassloader, but the intention is not fulfilled... Would the easiest change be to set it up so that a Block's Classloader is assigned t

Re: BlockThread

2004-01-02 Thread Niclas Hedhman
On Friday 02 January 2004 22:59, Fernando Padilla wrote: > Is there any reason why a new Thread is created and then kept around doing > and endless sleep loop ( sleeping for measely 300 millisec ), for every > block instanciation? This is _NOT GOOD_, I know that, and I think Steve knows it by now,

Repository and Merlin

2004-01-02 Thread Fernando Padilla
So I was looking at the Repository documentation on the website; I'm wondering about the Merlin Kernel loading code difference between the Repository Tutorial and the Merlin Sample Code we've been discussing. http://avalon.apache.org/repository/start/tutorial/index.html The tutorial uses the

Re: BlockThread

2004-01-02 Thread Berin Loritsch
Fernando Padilla wrote: Is there any reason why a new Thread is created and then kept around doing and endless sleep loop ( sleeping for measely 300 millisec ), for every block instanciation? Could we have the sleep loop be longer ( 10 sec ), and use interrupt to wake it up out of sleep if nee

BlockThread

2004-01-02 Thread Fernando Padilla
Is there any reason why a new Thread is created and then kept around doing and endless sleep loop ( sleeping for measely 300 millisec ), for every block instanciation? Could we have the sleep loop be longer ( 10 sec ), and use interrupt to wake it up out of sleep if need be? Could we create a

cvs commit: avalon-sandbox/avalon-net/Castle Castle-compilations.build README.txt

2004-01-02 Thread hammett
hammett 2004/01/02 05:27:00 Modified:avalon-net/Castle Castle-compilations.build README.txt Log: Castle MX Remoting infraestructure Revision ChangesPath 1.2 +5 -0 avalon-sandbox/avalon-net/Castle/Castle-compilations.build Index: Castle-compilations.build