[Http-crcsync] General comments on crcsync document

Pedro R eusou15 at yahoo.com
Wed Jul 8 22:23:23 EDT 2009


>>By using the OPTIONS method, the non-crcsync server may not respond
>>properly.

>which tells you what you need to know, right? (that its a non-crcsync
>resource.)

Yes, but I don't want to know if it is a crcsync resource or not, I just want the
request served without having to send another. If the request is crcsync, then OK,
if not, no problem, it gets processed the regular way.

What about another way: no crcsync headers are sent by the client, except for
"crcsync" appended to "Accept-Encoding:"?
When the server detects that a client accepts crcsync, it will send the crcsync
block response.
That way, the server is free to response in every way it feels apropriate and the client 
does not need to send any extra headers, saving a few precious bytes.

Don't forget that gzip and deflate work exactly the way described above, after all
crcsync serves a similar purpose.

Pedro


      


More information about the Http-crcsync mailing list