Vjeran Marcinko wrote:
----- Original Message -----
From: "Berin Loritsch" <[EMAIL PROTECTED]>
To: "Avalon framework users" <[EMAIL PROTECTED]>
Sent: Monday, June 16, 2003 2:21 PM
Subject: Re: [Fortress] Erasing objects in Poolable handlers
It would also be easy enough to send a patch to the RepeatedCommand that
manages the pool sizes so that we can check for validatable pooled
items.
Although, I do have to ask, why do you feel that you need to do this
for a component?
Well, currently I have component that encapsulates socket connection to my
special-purpose message server. Socket connection is established in initialize()
method. Since opening socket connection is time-consuming, I wanted to maintain pool
of this components through Poolable handler for reuse. And now I would like to erase
the component instance from pool in case this connection becomes broken for some
reason.
Since there's no way to do it right now, I'm solving the problem by creating again new
internal socket thus making this component valid again.
We do have the Resettable interface which is where this would be able to
occur. Alternatively, you could have a single component which handles
its own pool of connections as opposed to having a component bound to a
connection. Depending on the type of communication happening, the
alternative *could* open itself to load balancing accross the open
connections.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
