My 1st guess would be to use EHCache. it has swapping to disk, and you can set refresh policies i.e. data not read within the last 5 minutes is considered stale.
Cheers, Renier _____ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Jeff Mutonho Sent: 02 February 2007 15:01 To: [email protected] Subject: [CTJUG Forum] How would you do this? A SFSB talks to a webservice that brings back lots of data.The data never needs to be persisted.It's just viewed(read only) by many many clients at a time.A client can open a session to view the data and leave the session running for many hours at a time.When they (the client) need to view the data again after some passive time , then data has to be refreshed, so that they see uptodate data.Since the SFSB communicates with the webservice , how best can it do the caching of the large volumes of data it receives , whilst ensuring that whenever a client who has been passive for the last , say hour , will see fresh (uptodate)data..i.e how should the SFSB handle refreshes? How would you design /architect solution for such a scenario? -- Jeff Mutonho Cape Town South Africa GoogleTalk : ejbengine Skype : ejbengine Registered Linux user number 366042 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CTJUG Forum" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/CTJUG-Forum For the ctjug home page see http://www.ctjug.org.za -~----------~----~----~----~------~----~------~--~---
