> I do not find either of these solutions attractive. The stateful
> session bean
> will compromise scalability by allocating memory for each user, while,
> if I am
> not mistaken, the httpsession object will attempt to download cookies to
> the
> browser's host--an attempt that is not guaranteed to succeed. My
Most servlets check for the cookie capability, and if it is not available
use URL munging to ensure the session info is managed properly. However,
this requires that you pass all of your URL's through an encoder method.
> preferred
> solution is to keep some of the state in hidden input controls within
> the HTML,
> amongst which would be a GUID by which bulkier quantities of state (more
> than a
> shopping basket: the responses to a survey or regulatory form for
> example) can
> be retrieved from a data store.
I agree in that I like to only have a "session id" in my servlet, which
in turn points to greater context in a more efficient store.
tim.
Tim Endres [EMAIL PROTECTED]
ICE Engineering, Inc. http://www.trustice.com/
"USENET - a slow moving self-parody" - Peter Honeyman
===========================================================================
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".
