Robert Castaneda wrote:
>
> A combination can be used:
>
> One could easily write Stateful beans as clients to the Stateless beans to
> be used for WAP and thin client apps, and stateful clients with Stateless
> Beans for transaction heavy use for scalability reasons

That would result in different facades for different clients. IMHO this
would cause a somewhat confusing architecture, and in that case I would
prefer to have the WAP servlet keep the session for itself.

/Marcus

Marcus Ahnve
Sun Java Center
Sweden

===========================================================================
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".

Reply via email to