[Http-crcsync] First contact with a crcsync server

[Pedro R]

Hello

In the early stages of the adoption of the crcsync protocol, it will be 
quite inneficient for a client to send the crcsync headers in every 
request which is made. So there must be a way for a client to identify a 
crcsync server (once it is identified it is added to a whitelist and 
subsequent requests will always have the crcsync headers).


Right now my client (a Firefox extension) is in embrionic stage, but 
I'm doing a few experiments, and I've noticed that if I send "If-Block: 
0" along with the other crcsync request headers, I get what I believe to 
be the all the blocks. I'm not sure of this is true or not, I can only 
assume it from reading the server log, because on the client side I'm not 
re-assembling the response.

[Wed Jul 08 21:27:23 2009] [debug] mod_crccache_server.c(207): CRCCACHE-
ENCODE Block Hashes header found so enabling protocol: 0


So is my assumption true? And if it is, can you make this official in the
protocol? This way, a client can add the server to the whitelist, save 
the block encoded response and reassemble it for the upper layers right 
upon first contact.

Pedro Ribeiro