Laurel Neustadter wrote:
>
> According to a Gemstone paper on theserverside.com, stateful session beans
> aren't scalable (due to the activation/passivation expense, creation
> expense). According to that article, if the number of users will ever grow
> to beyond a few thousand, stateless session beans should be used. Of course,
> the exact numbers must be server-dependent. But it seems scalability is
> another consideration when choosing between stateful/stateless session
> beans.
Poor (or simplistic) server design may mean that even passivated SFSBs occupy
significant memory. But it's not intrinsic to Stateful Session Beans.
> The URL for the article is
> http://theserverside.com/resources/article.jsp?l=ICommerce-Design-Strategies
> #stateful.
It's a good article for telling you how to ensure scaleability when using
Gemstone/J but should not be interpreted too broadly.
cheers... Ian
========================================
Ian McCallion
Alexis Systems Limited
Romsey, UK
Tel: +44 1794 514883
Fax: +44 1794 501692
========================================
===========================================================================
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".
