> I prefer to use pooled objects either for relative small number of
> long lived objects or for objects that are expensive to create, or
> immutable objects that consume some memory and are likely to be in
> use concurrently.
And what you think about objects that are created millions of times
On Tue, 2003-02-04 at 00:34, Ralph Einfeldt wrote:
> I prefer to use pooled objects either for relative small number of
> long lived objects or for objects that are expensive to create, or
> immutable objects that consume some memory and are likely to be in
> use concurrently.
Pooling is actuall
lean(true)
> -Original Message-
> From: Will Hartung [mailto:[EMAIL PROTECTED]]
> Sent: Monday, February 03, 2003 11:42 PM
> To: Tomcat Users List
> Subject: Re: Object pooling (was: more about custam tag life cycle)
>
>
> > From: "Erik Price" <[EM
Will Hartung wrote:
From: "Erik Price" <[EMAIL PROTECTED]>
Sent: Monday, February 03, 2003 2:16 PM
Subject: Re: more about custam tag life cycle
Are you saying that in general, object pooling is deprecated? In other
words, it's always a bad idea, with the exception of DataSource type
poo
> From: "Erik Price" <[EMAIL PROTECTED]>
> Sent: Monday, February 03, 2003 2:16 PM
> Subject: Re: more about custam tag life cycle
> Are you saying that in general, object pooling is deprecated? In other
> words, it's always a bad idea, with the exception of DataSource type
pools?
As a design i
