cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Arjé Cahn <>
Subject RE: Backend cache invalidation
Date Fri, 23 May 2003 14:30:26 GMT
> > This is a pull-mechanism to fetch objects from your database. 
> > PUSHing them into the cache (what you suggest) might be a bit 
> > more difficult.
> > 
> Huh? Don't understand what you're getting at. 
> I'm not trying to change anything in the way the Cocoon 
> caching mechanism
> works (and I've looked at the Cocoon code and know how it 
> works).  All I'm
> looking to do is introduce a new cache validity object that 
> knows when to
> stop signaling valid (true) as a result of the back end 
> telling it that it
> is in fact no longer valid...

Okay, so you already know. I'm sorry - thought you didn't have a validity object at all..

I actually thought you wanted to PUSH your new data into the cache. Which sounds pretty cool
anyway. This as opposed to getting it from the database on request (and waiting a long time
for the response).


View raw message