Hello, My project needs to add flexibility such that when our real data source goes offline, JCS continues to return the cached items until some point later when we bring the DB back online. We will handle the condition gracefully when a non-cached item is requested during the downtime. The idea is to keep the content flowing for those users who are already logged in and are only requesting cached items.
The items returned by the cache are normally time-bound (in fact, they are user session objects) - so we normally use the cache parameter "MaxLifeSeconds" so they expire automatically. Is there a way to disable the MaxLifeSeconds parameter and re-enable it later? If not, I'm also considering storing wrapper objects for everything in the cache, that contain both the real object I'm storing and an insertion millis value. We would perform the timeout logic ourselves - and remove the MaxLifeSeconds completely. Has anyone tried this? -- View this message in context: http://www.nabble.com/Hot---on-the-fly-update-of-config-tp17364367p17364367.html Sent from the JCS - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
