[Http-crcsync] Apache proxy CRCsync

[Toby Collett]

Hi Alex,
I think you are on the right track, there is a third option which is to add
a few extra configuration options to the cache module to make it more
aggressive about caching. Basically to cache everything except pages marked
'private' (and possibly even them as long as you can ensure the server is
secure).

Another aspect of our use of the cache module at the moment is that the disk
cache modules has a large portion of code in common with the client module.
It would be nice to add a few hooks to this module and reduce our code
duplication.

That being said, a module that doesn't require modifications to the apache
source is an advantage, however I think header hacking would be the only way
to achieve this so probably we cant get away with this.

Martin's comments about the garbage collection (which just arrived) are an
important consideration otherwise the cache could get out of control quite
quickly.

Toby
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.laptop.org/pipermail/http-crcsync/attachments/20090324/3a451590/attachment.htm