You may consider using JCS, I've done some research into for a project but never actually used it. It's caching mechanism and it will allow you to specify the in-memory size and expiration on your data.
Cheers, Ivan ----- Original Message ----- From: "Simon Kelly" <[EMAIL PROTECTED]> To: "Struts Users Mailing List" <[EMAIL PROTECTED]> Sent: Monday, March 03, 2003 10:00 AM Subject: Re: Best place to syncronize within struts. > > ----- Original Message ----- > From: "Jacob Hookom" <[EMAIL PROTECTED]> > To: "'Struts Users Mailing List'" <[EMAIL PROTECTED]> > Sent: Monday, March 03, 2003 3:55 PM > Subject: RE: Best place to syncronize within struts. > > > > Synchronization should take place at the lowest denominator possible. > > By this I take it you mean as close to the actual call to the db as > possible? > > > The other thing to do is create a caching filter for your web content > > that stores the page for 2-5 minutes before it refreshes itself. > > In the whole application the data will be entering the db every 5 seconds or > so from the other end so caching may cause some critical data to be missing > from any given access. > > Thanks for the info though, I will look into both of them. > > Cheers > > Simon > > > > > > --------------------------------------------------------------------- > > 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] > > > > > > > --------------------------------------------------------------------- > 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]
