[Http-crcsync] General comments on crcsync document

Patrick McManus mcmanus at ducksong.com
Thu Jul 9 16:39:55 EDT 2009


On Thu, 2009-07-09 at 21:36 +0200, Alex Wulms wrote:
> All,
> 
> I would expect a client to perform a standard GET request for it's first 
> request to a server. A crcsync-aware server should then advertise it's 
> capability in a response header so that the client can use a delta-request 
> the next time that the user wants to refresh this resource.
> 
> Keep in mind that on the first request, the client won't have anything in the 
> cache from this server; it is a first request after all... So there is no 
> overhead at all in this approach (except for the small capability response 
> header)
> 
> Obviously this is suboptimal at the moment that a non-crcsync-aware 
> server -from which the client has already received normal responses- gets 
> upgraded to a crcsync-aware server; the first request that the client will 
> send after such an upgrade would still be a normal GETrequest. However, the 
> now crcsync-aware server should at that moment announce it's capability so 
> that the client can switch to delta-requests after all.
> 
> What do you think?

I'm happy to say I think we're all in sync on this one.. just a matter
of defining that response header.





More information about the Http-crcsync mailing list