Re: mod_cache and the proxy.

rbb@covalent.net wrote:

> Well almost, but not quite. In order to do this, the proxy would need to

Ok.

> It isn't close at all. My prototype module is basically just a filter

I had this problem when I did the HTTP/1.1 patch - I rewrote much of the core stuff within the proxy.

> What still needs to be done to mod_cache.c:

Multiple backends I assume means a shared memory backend, a disk backend, etc?

Do you need help?

In addition to our free technical library, Pantek provides professional IT services to companies who utilize Open Source software: Learn more about Pantek's Technical Support offerings Place an order for 24/7/365 Technical Support here Learn more about Pantek, who we are, and what we do Chat with a Live Operator Related httpd.apache.org Links announce bugs cvs dev docs gui-dev modproxy-dev packagers testers Request more information about Pantek

> Cache entries should be stored in a hash table that uses the key values:

What I want to do is build in content negotiation into that as well. In other words, you provide hostname:port/URI *and* the request headers, and based on both you get a response back. This will allow you to cache both an English and French representation of the same URL, or a compressed and non-compressed representation of an URL at the same time.

> Once the handler is written and the filter can get the correct location to

This effectively represents the caching filter part of the design I proposed. What is needed now is a content-generator entity that optionally returns cached data if it exists, or DECLINED if not.

These two together will make the start of a working cache.

Regards,
Graham

-- 
-----------------------------------------
minfrin@sharp.fm		"There's a moon
					over Bourbon Street
						tonight..."