[Http-crcsync] crcsync, Mozilla, GSoC and students

[WULMS Alexander]

Hi Gerv,

We have configured one Apache server with two virtual instances. One as decoding proxy and the other one as encoding proxy.

E.g. browser <-> decoding virtual server <-> encoding virtual server <-> origin server

In your setup it would become:
Browser <-> encoding virtual server <-> origin server

See the docs folder in the repository on how to make the above setup. All required apache config files are present and some readmes
on how to use those config files for Ubuntu and for SuSE.

Thanks and brs,
Alex



--------
Alex WULMS
Lead Developer/Systems Engineer

Tel: +32 2 655 3931
Information Systems - SWIFT.COM Development
S.W.I.F.T. SCRL

>-----Original Message-----
>From: http-crcsync-bounces at lists.laptop.org [mailto:http-crcsync-bounces at lists.laptop.org] On Behalf Of Gervase
>Markham
>Sent: Wednesday, April 08, 2009 11:25 AM
>To: Alex Wulms
>Cc: http-crcsync at lists.laptop.org
>Subject: Re: [Http-crcsync] crcsync, Mozilla, GSoC and students
>
>On 07/04/09 20:56, Alex Wulms wrote:
>> Hi Gerv,
>>
>> Here is what they need:
>
>Hi Alex,
>
>Thanks for that info. However, I was more asking the question "how do
>they set up a system which is the same as the one you are using for
>testing?", rather than "what should they do to port this code to
>Firefox?". :-)
>
>Do you guys test by passing data from the website to one caching Apache
>to another caching Apache and then on to the browser, and look between
>the two Apache instances to see what's happening? Or some other method?
>How do you set up your test environment?
>
>> Basically, mod_crccache_client.c is an apache cache handler module. It takes
>> care of building the "Block-Hashes" request header and of re-assembling the
>> final response from the originally cached file and the encoded data received
>> from the upstream server. Because it integrates with apache, you can not just
>> take it as is, but you will have to port the code into firefox.
>> But the good point is that it is build on top of the code in ccan/... folder,
>> which is completely re-usable.
>
>Brilliant. I'm sure at some point we can talk about licensing
>compatibility ;-)
>
>> Note that the code is not yet complete.  It is only a first draft of the
>> implementation. There are still several special cases that need to be
>> supported. See all TODO remarks in the code and the discussions about the
>> protocol specification on this list.
>
>Indeed. I am hoping that the successful student will take an active part
>in this list and the development of the protocol.
>
>Gerv
>_______________________________________________
>Http-crcsync mailing list
>Http-crcsync at lists.laptop.org
>http://lists.laptop.org/listinfo/http-crcsync
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 5020 bytes
Desc: not available
Url : http://lists.laptop.org/pipermail/http-crcsync/attachments/20090408/90783b53/attachment.bin