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
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
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
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
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
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
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,
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
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
