The best strategy is to use an entity bean and use a server that
supports caching them.
Caching is a quality of service attribute of a server. Your entity will
be more efficient on servers that support entity caching but will still
work on any server.
Since session beans are designed for a single client, attempting to
using their state as a multi-user cache contorts the model and will
likely lead to non-portable code.
Steven Lewis wrote:
>
> Nice feature of a stateful session is that it is a singleton
> so in a cluster we do not have to worry about synchronization of multiple
> copies
>
> At 06:46 AM 6/28/2000 +1200, you wrote:
> >Steven Lewis wrote:
> > >
> > > Shared Stateful Session
> > > ...
> >
> >Wouldn't it be simpler to use entity beans backed up with some kind of
> >read-cache?
> >___________________________________________________________________________
> >_____
> >
> >Evan Ireland Sybase EAServer
> >Engineering [EMAIL PROTECTED]
> > Wellington, New Zealand +64 4
> > 934-5856
> >
> >===========================================================================
> >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".
>
> ==============================================================
> LordJoe - Java Training and Consulting
> http://www.LordJoe.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".
===========================================================================
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".
