Re: Current plan

> So far many of the caching thoughts that have gone past haven't taken

Great. You and I are on the same page. You posted something to new-httpd about a new caching framework, that uses filters. Let me add to it. :-)

Basically, the current cache is a hack, and we need to remove it. The basic design for the cache should be simple, we are allowed to cache anything, including the output of a php function call. To do this, we have a very light-weight cache framework, that does garbage collection.

The actual cache'ing work is done with a single cache filter (basically written and working). To cache to different data stores, you just use a different plug-in to the filter. I am thinking that just the write and read functions need to be replaced for each plug-in. This will look seamless to the user. Oh, I guess we also need to plug-in different remove functions so that we can do GC sanely.

I will post the filter when I get a chance to clean it up a bit more. I am not going to bother putting in the logic to figure out the correct filename for the cache, but I do want to make it obvious how different data stores can be plugged in.

Ryan

Ryan Bloom                        	rbb@apache.org