Use a cache that times out. If you implement a cache that will defer lookups for 30 seconds or so (configureable!), then you will get the behaviour that John described after the timeout but still get the performance gains from having a cache.
There is an implementation of such a time-out cache in the Turbine code base.
Too right you are. I will use this for my own application which is based on Turbine anyway. I was thinking about a general solution which can be built into Torque. I guess using a Turbine Service is not an option there.
Bye, Thomas.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
