You may really want/need the transactional integrity provided by the dbms if you are combining queries (on possibly different caching intervals) in a client single response.
As Geoff implies the approach you mention could provide stale data for as long a 59.99999...secs depending on the frequency of insert/update/delete. Rigging up a load test with the real queries/db will tell you if this is an issue...
HTH Steve
rufio wrote:Hi all Is there a way to enfoce an asumption that volatile data (eg. stored in DB) changes once a specific interval?
Now if we have 100 requests/s SQLTransformer querys DB 100 times/s, right? I'd like to set it up to query only once a, say minute and cache the result.
To my knowledge there is no way to do this with the current SQLTransformer. You could extend the SQLTransformer to add caching support which would be quite trivial to do if you are really content to use such a simple algorithm as cache always for one minute.
Geoff
_________________________________________________________________
Add photos to your messages with MSN 8. Get 2 months FREE*. http://join.msn.com/?page=features/featuredemail
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
