:53:15AM -0600, Waldhoff,
Rodney wrote:
That should probably be SoftReference--so that the
pooled object may be
gc'ed if memory is tight.
-Original Message-
From: Slawek Zachcial
To: [EMAIL PROTECTED]
Sent: 1/25/02 3:16 AM
Subject: ObjectPool - weak reference based impl
Hi,
I noticed that on the pool todo list there is the
action to implement weak reference based pool.
Can someone explain to me what is the reason/need
behind? Should the idle pool objects be stored with
weak references?
My understanding is that you use object pool to avoid
the unnecessary
:
That should probably be SoftReference--so that the pooled object may be
gc'ed if memory is tight.
-Original Message-
From: Slawek Zachcial
To: [EMAIL PROTECTED]
Sent: 1/25/02 3:16 AM
Subject: ObjectPool - weak reference based impl
Hi,
I noticed that on the pool todo list
Subject: ObjectPool - weak reference based impl
Hi,
I noticed that on the pool todo list there is the
action to implement weak reference based pool.
Can someone explain to me what is the reason/need
behind? Should the idle pool objects be stored
with
weak references?
My
