> > >Well, we "only" need a fast mechanism to access an equivalent of a timestamp >for a node. There's a unique (and timestamped) id for each write operation >made by Slide (that's the transaction xid). By associating the "timestamp" >with the uri in a special store, we could easily do cache revalidation. > Thanks Remy - I see where your coming from here - makes perfect sense.
Question tho: Shouldnt the timestamp be determined by the contentstore provider? My principle concern is more about the validity/integrity of the data rather than the performance aspects. Is there any simple way for a client app to to force a refresh of the cache (without 'writing' anything)? Regards, Andy Scholz
