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
