Yes I mentioned the callback stuff but actually my personal preference would
be to lazy load the data...
The only thing I could think of would be those that are annoyed because they
are loading a fair amout of data taking then a hit. Generally they don't
want to delay the load so that the one who needs first the data doesn't
incur this hit (but IMO it has its own drawback such as what you do if there
is no data yet, even though I would likely try to see if all those data
wouldn't belong actually to distinct smaller caches)...
Patrice
--
"Brock Allen" <ba****@NOSPAMdevelop.com> a écrit dans le message de
news:62**********************@msnews.microsoft.com ...
Thats a good suggestion Patrice. There is a callback event you can
hook when the cache item expires, and during the event processing
Jensen could update the cache entry.
But again, why do it this way? It's usually much easier to just lazy load
the data upon the next request for it if the Cache has timed out. *shrug*
-Brock
DevelopMentor
http://staff.develop.com/ballen