Sam Magnuson wrote: > > Chuck Murcko <[EMAIL PROTECTED]> writes: > > > Sam's patch from a3 went into 2.0 today, with some modification for the > > changes in layout, config, etc. This uses mod_cache and the nascent > > caching API, which may need to be reconsidered in light of the proposed > > table processing changes. > > > > Great, I'm glad it has been accepted. I guess the caching stuff isn't > exactly modproxy specific - but when design does happen, I would like to > offer my services to whomever does pick it up, and assist where needed. > > As proof of concept - mod_shmem_cache should be ready for general > consumption should anyone be interested it is at: > > http://libre.aventail.com/~smagnuson/dists/sam-mod_shmem_cache+apache_2.0a3v1.tar.gz >
Yeah, there's a lot of work still on the existing proxy and file cache, converting to APR, etc. You might want to do that now for the mod_shmem_cache so it doesn't quite cause the uproar this patch did. > > Next step is cleanup, HTTP/1.1, testing, and other fixes. > > > > This should be considered a reference proxy for 2.0, and perhaps will > > end up being the backwards compatibility mode of the actual 2.0 proxy. I > > know there are a number of people > > with code and good ideas about where to go with the proxy, so please do > > not consider this > > a design fixed in stone. > > > > Hopefully a few people will now come out of the weeds on the > > modproxy-dev list. 8^) > > Indeed, thanks for setting this up Chuck. > -- Chuck Chuck Murcko Topsail Group [EMAIL PROTECTED]
