Laurel Neustadter wrote:
>
> Isn't this app server (or web server) dependent?
>
> For example, an alternative design is to store only a session id on the
> client and store the rest of the session data in some persistent server-side
> store, such as a DBMS. I believe this is the approach WebSphere Application
> Server 4.0 takes, for example.
I was not aware that WebSphere did this. I hope their Stateful Session Bean
Passivation does the same thing :-)
> Maybe I am misunderstanding what you mean by "HTTPSession data goes up and
> down the wire between the client and the web
> server.".
No, you are not misunderstanding.
I still hold to the view that keeping client state information in a SFSB is the
right design point, unless your chosen app server's SFSB implementation does not
scale sufficiently for your needs.
========================================
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".
