[Http-crcsync] http-sync standard

[Alex Wulms]

Op maandag 6 april 2009, schreef 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.
I suppose that once this delta-protocol is well established, that the leading 
CMS frameworks will adapt and use for example a versioning system to keep 
track of all the versions of a page/document/content-fragment and easily 
generate the delta compared to the version that the client has in cache.

This transition process would probably be lead by sites targeting users on 
low-bandwith connections. They could ask their respective CMS suppliers (be 
it open source or proprietary solutions) to build good support for http-rsync 
into the CMS systems.