Yes, persisting the session data in a database is the obvious answer. No question that I agree with that.
However, I was trying to find a solution that would get a bit "EJB-happy". I guess, I am not really sure myself what I am asking... I was just trying to stretch the use of Stateful EJBs and its handle, but the question didn't come out right... Never mind. Sorry for wasting your time and thanks for your replies anyway. Thanks, Yaakov. -----Original Message----- From: Larry Meadors [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 26, 2005 5:48 PM To: Struts Users Mailing List Subject: Re: [Very OT] Hypothetical challege On Wed, 26 Jan 2005 14:40:11 -0800, Wiebe de Jong <[EMAIL PROTECTED]> wrote: > > If you don't like the performance hit of going to the database every time, > then add a plugin. When the application starts, the plugin will read all the > sessions from the database into memory. When the application ends, the > plugin would write out all the sessions to the database. Or, use JMS to write the changes, so they happen asynchronously. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
