i don't know if it's possible that the resource itself can know if it was modified etc. or even it is cacheable at all. i think the most it could do is to provide some sort of dependencies. but i think an overall caching service can control the cache states of the resources. the respective filter/servlet that delivers the response will then set the appropriate cache headers.
regards, toby On 1/10/08, Padraic Hannon <[EMAIL PROTECTED]> wrote: > Bascially, you would want a resource to be able to let a caller know > if it is stale? > > -paddy > > On Jan 10, 2008, at 12:44 AM, Felix Meschberger wrote: > > > Hi, > > > > Am Donnerstag, den 10.01.2008, 03:02 +0200 schrieb Jukka Zitting: > >> Which brings me to my followup point: How does Sling support HTTP > >> caching? Is there something we should do to improve that? As a > >> "RESTful" web framework, Sling should IMHO have built-in support for > >> things like ETags, Expiration headers, 304 responses, etc. > > > > Currently Sling has nothing in it. But since this issue has been > > brought > > up in the Sling BOF in Atlanta, we certainly will have to think about, > > how we could provide support for that. > > > > But for the moment, there is no concept around yet (hint hint :-) ). > > Maybe something around the Resource interface along the lines of how > > Excalibur [1] does it ? > > > > Regards > > Felix > > > > [1] > > http://excalibur.apache.org/apidocs/org/apache/excalibur/source/SourceValidity.html > > > -- -----------------------------------------< [EMAIL PROTECTED] >--- Tobias Bocanegra, Day Management AG, Barfuesserplatz 6, CH - 4001 Basel T +41 61 226 98 98, F +41 61 226 98 97 -----------------------------------------------< http://www.day.com >---
