Huh? I don't think so. If you read our architecture white paper we endorse a
"service" layer that is manifest as session beans. See the white paper at
http://www.javasuccess.com/
It may have been Stateful session beans that were being referred to, which
could be a barrier to scalability since they are more resource intense.
Regards,
-Chris.
> -----Original Message-----
> From: Robb Greathouse [SMTP:[EMAIL PROTECTED]]
> Sent: Thursday, June 08, 2000 5:51 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Scaling problems with session beans.
>
> I was just at Java 1. A Gemstone speaker was saying that having session
> beans represented a serious architectural flaw and a barrier to scaling.
>
> Does anyone have information on the problem and alternatives when tracking
> a users state is critical?
>
===========================================================================
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".
