On 07.05.2011 15:44, Markus KARG wrote:
> Decoupling is just a means to get a particular improvement, not an
> improvement by itself - but it is added complexity and such adds possible
> cause of failure. So what will *this* decoupling actually provide *here*,
> despite the problems I already mentioned in my last posting?
> ...
Well, decoupling would require us to define a proper caching API, which
isn't trivial, but might help implementers get their code right.
Consider all the things you have to get right:
- properly handling Conneg (Vary...)
- special casing Cookies
- working around server bugs with compression
- properly handle extension status codes/methods
- invalidation
- heuristic expiry
- parsing Cache-Control/Pragma
- range requests
etc.
Don't get me wrong, it would be awesome to get a clean Java
implementation of the HTTP caching model; optimally following what the
HTTPbis WG is doing in
<
http://greenbytes.de/tech/webdav/draft-ietf-httpbis-p6-cache-14.html>.
Best regards, Julian