"Craig" wrote:
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
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.
--------------------------------------------------------
There will always be sacrifices in any designed solution. From the
above,
I would say that you're sacrificing security (hidden form elements),
unless
you're encrypting them (in which case you're usually taking a
performance
hit). Also, if you now have state in your DB, you're making x number of
DB
calls with manipulations/marshalling into the proper variables.
Overall, there is no one size fits all solution. I think many of the
suggestions
have merits in different situations. This is one of those religious
discussions....
m.
===========================================================================
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".
