|
One of the recommendations is to use
HttpSessions unless you need to support non-Web clients.
Scott Stirling JRun QA Macromedia
Hi,
I'm curious how everyone else has designed their system to maintain
state. Are most of you maintaining state on the presentation tier until
the user is ready to submit and save their changes? Are you putting your
ValueObjects in the HTTPSession?
Or, are any of you using Stateful Session Beans to maintain your state on
the Business Tier. Passing ValueObjects as the user goes from page to
page. Then, when the user is ready for the final save, inform the
Business Delegate to persist the data.
Is there a recommendation in the J2EE Patterns on which direction to
go? I've read all of them, but for some reason, can't think of this
being discussed.
Thanks for any feedback!
Dawn
Dawn L. Lewis Southwest Airlines Fuel Managment, Systems
Department (214) 792-3966 [EMAIL PROTECTED]
|