Sorry, I must have missed the earlier part of this thread.
When you say pool references are you talking about
interfaces obtained through a home interface or do you
mean ejb-references.
If the former, won't your pool contain references to beans
that may passivate? Or perhaps a more general question:
how can you be sure the references in your pool stay valid?
thanks.
Avi Kivity wrote:
> >
> > Other solutions:
> > - cache the remote references per thread.
> >
> Also, you can create a pool of remote references or home references, thus
> avoiding single-threading your client.
>
> You would use the pool as follows:
>
> StatelessRemoteRef ref =(StatelessRemoteRef)pool.acquire();
> try {
> ref.method();
> } finally {
> pool.release(ref);
> }
>
> The pool would create remote references on demand in a thread-safe manner.
>
> - Avi
> --
> s/\be(\w+)/e-\1/g;
>
> ===========================================================================
> To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
> of the message "signoff EJB-INTEREST". For general help, send email to
> [EMAIL PROTECTED] and include in the body of the message "help".
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
