Yeah, I know... but we're running Windows and while our Test site supports CAS, we haven't rolled that client/server mix into production yet. They tell me that, sometime this year, that will happen but, until then, I have to do it old-school.
On Fri, Oct 3, 2008 at 1:02 PM, Dustin <[EMAIL PROTECTED]> wrote: > > > On Oct 3, 3:51 am, "Josef Finsel" <[EMAIL PROTECTED]> wrote: > > > The way I've implemented it is to cache objects that contain a refresh > time > > stamp. First call that gets an item after the refresh time, immediately > > updates memcached with the a refresh time = expiration and then > repopulates > > the object. Any calls made between the point in time the refresh time is > > reset and the object is refreshed in the cache get stale data. > > > > That does also require some other code to handle the possibility that > more > > than one process is going to try to get the data but all of this has been > > implemented in the standard data layer so it's very easy to implement. > > The CAS or at least add semantics are pretty much created for this > type of thing. > -- "If you see a whole thing - it seems that it's always beautiful. Planets, lives... But up close a world's all dirt and rocks. And day to day, life's a hard job, you get tired, you lose the pattern." Ursula K. Le Guin
