[Http-crcsync] General comments on crcsync document

[Alex Wulms]

I have checked-in an updated version of the server module and the protocol 
document. The server now updates the ETag header as previously discussed. 
That is: it appends -crcsync-<original-encoding>, with <original-encoding> 
the content-encoding that was used by the origin server.

Basically, the server now properly implements all mandatory response headers.

The optional 'Crcsync-Similar' and 'Capability' headers are still missing. 
I'll add them in the course of the coming week(s).

The client-module (I did not change it now but just for your information) 
currently understands all mandatory headers. Though, it does not yet 
re-encode the content with the original content-encoding before delivering to 
the downstream client. It simply delivers it in 'identity' content-encoding. 
Re-encoding the content is a future enhancement.

PS: I made some error during the git push. There are now two different labels 
in the repo. An 'origin/master' label on the latest push by Toby and 
a 'master' label on the latest push by myself. I hope this does not confuse 
clients when doing a 'git pull' or so. Furthermore, I don't know how to fix 
the labels in the repository. Git is still somehow a mystery to me.

Cheers,
Alex



Op zondag 3 januari 2010, schreef Pedro Ribeiro:
> On Wed, Dec 30, 2009 at 12:03 PM, Gervase Markham <gerv at mozilla.org> wrote:
> > On 30/12/09 10:25, Martin Langhoff wrote:
> >> On Wed, Dec 30, 2009 at 9:59 AM, Alex Wulms <alex.wulms at scarlet.be> 
wrote:
> >>> The only important point not yet well implemented in the apache crcsync
> >>> modules is the handling of etag (it is not yet implemented as
> >>> previously discussed) and re-compressing the content by crcsync-client.
> >>> I'll add this part to the code.
> >>
> >> Yay! Woohoo!
> >>
> >> WRT the Firefox GSoC... there are some updates here
> >> http://firefoxcrcsync.wordpress.com/ - I think the dev is Yin Qiu, so
> >> CC'd...
> >
> > No, the developer was Pedro Ribiero: eusou15 at yahoo.com (CCed). I haven't
> > heard from him since the end of GSoC unfortunately. Perhaps he can
> > update us on his progress? :-)
> >
> > Gerv
>
> Hi all,
>
> sorry for the late reply, just arrived today.
>
> Progress is going slowly, I haven't had much time!
>
> There is a lot to do, as there has been a lot of activity in the
> http-crcsync git. The firefox-crcsync code only reflects what was done
> till 2009-07-30. On top of this, most of the GSOC code was pretty much
> non-working except in special conditions, these also need to be
> cleaned.
>
> I need a couple of weeks to get the code properly working again and
> implement the changes above. I'll keep you guys posted on the
> progress...
>
> ... and ask stupid questions!
>
> Regards,
> Pedro
> _______________________________________________
> Http-crcsync mailing list
> Http-crcsync at lists.laptop.org
> http://lists.laptop.org/listinfo/http-crcsync