Rickard �berg wrote:
> Hey
>
> Chuck Zheng wrote:
> > I know this is an implementation specific question. But I am interested
> > in knowing what strategies vendors are using to minimize resoruce
> > consumption therefore improve scalability.
>
>
> I'm fiddling with an approach that instead uses 1 (one) EJBHome and 1
> (one) EJBObject per bean. If you think 5 minutes about it is is not that
> hard to figure out how to do it, and it is *much* more efficient IMHO
> than the brute force method. In this case you would never have to worry
> about DGC or such issues, because you would never have idle EJBObjects
> around. A nice sideeffect is that you can entirely skip the "create
> container-specific EJBObject implementations"-phase.
>
> /Rickard
Back in April of this year there Per Spilling started a short thread talking
about this very topic. I have provided link (below) to the posting in the
archive. To follow this thread to its conclusion clicking on the "Next in
topic" link in the view section at the top. I think you will find this
discussion very informative.
http://archives.java.sun.com/cgi-bin/wa?A2=ind9904&L=ejb-interest&P=R2922
Rickard, is your idea basically the same as was suggested by Per in this thread?
Richard
--
Richard Monson-Haefel
Author of Enterprise JavaBeans
Published by O'Reilly & Associates
( http://www.monson-haefel.com )
===========================================================================
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".
