Dominic Cioccarelli wrote: > Just to clarify things, what I was attempting to say is that EJB server > vendors must resort to instance pooling to offset the performance > degradation imposed by the fact that multiple threads can't access the same > stateless session EJB simultaneously (i.e. EJB accesses are searalized).
No, they don't have to do that. That is one implementation option to achieve those results. Another option would be to instantiate instances on demand. > This wouldn't be necessary, say, for an RMI or CORBA server where a single > object can serve multiple clients simultaneously. But in that case concurrency must be handled manually. Which is fine, if you're comfortable with that. I'm just pointing out the differences. Value judgments is one thing, and knowing the differences is another. /Rickard -- Rickard �berg Author of "Mastering RMI" Chief Architect, TheServerSide.com The Middleware Company - We Build Experts! =========================================================================== 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".
