> As I understand it, Polipo caches only one variant for a negotiated > resource and serves this one based on the Vary, Content-* and Accept-* > headers. Is this correct?
Yes. > I'd like to implement Transparent Content Negotiation as described in > RFC 2295. Is this a good idea? I personally don't think so. It's a lot of work (both the in-memory and on-disk caches are indexed by URL, so you'll need to do quite a bit of work on the data structures), and most negotiated resources are dynamic pages, so they won't be reused anyway. For your particular application -- you only need to write out the other instances, not to read them back into Polipo. Why don't you just write out all downloaded instances a second time, straight into your git repository? A good place to do that is server.c around lines 2347 and 2377, which is are the two places where an instance is marked as being finished downloading. -- Juliusz ------------------------------------------------------------------------------ LogMeIn Central: Instant, anywhere, Remote PC access and management. Stay in control, update software, and manage PCs from one command center Diagnose problems and improve visibility into emerging IT issues Automate, monitor and manage. Do more in less time with Central http://p.sf.net/sfu/logmein12331_d2d _______________________________________________ Polipo-users mailing list Polipo-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/polipo-users
