[Http-crcsync] Apache proxy CRCsync & mozilla gsoc project?

[WULMS Alexander]

>
>If the cache just blows away the cached base page it was using when one of
>these errors occurs, that should Do The Right Thing even without seed.
I see some concurrency issues and race conditions if the cache would simply blow away the cached base page, just in case that two
different concurrent requests are using the same base page and only one of them suffers from the checksum clash.

I think using a random seed per request would indeed be a safer approach to handle the manual retry scenario 

Nevertheless, the chance on failure should indeed be reduced by using a stronger hash.

-------------- 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/20090402/656579a7/attachment.bin