[Http-crcsync] http-sync standard

[Martin Langhoff]

On Mon, Apr 6, 2009 at 8:07 AM, Toby Collett <thjc at plan9.net.nz> wrote:
> Slashdot is probably a bad example for most of this, as they seem to care
> very little about cachability (they mark their pages as private even).

Most CMSs today behave exactly like slashdot. Smart CMS frameworks
that manage to keep track of whether the zillion components that form
the page have not changed often use a SHA1 for the etag (similar to
what you propose...). But those are in the minority.

This content that is cacheable but marked not cacheable -- sadly
prevalent these days -- is often streamed right through to the client
-- the server doesn't set content-length and writes to the socket in
chunks.

cheers,


m
-- 
 martin.langhoff at gmail.com
 martin at laptop.org -- School Server Architect
 - ask interesting questions
 - don't get distracted with shiny stuff  - working code first
 - http://wiki.laptop.org/go/User:Martinlanghoff