David Steinbrunner wrote:
> In an effort to figure out more about the reasoning of the caching I started > looking over the docs more and found the PROTECTED METHODS section that > talks about the _get_cache and _set_cache methods. At that point I had the > bright idea of sub classing them so that I could get my code out of > CGI::Application::Dispatch and into my own Dispatch subclass that is already > overriding http_error. That did not go so hot since neither _get_cache or > _set_cache ever get called. Looks like _url_cache has replaced the above > methods and the docs never updated to reflect that change. Whoops. I think those were planned additions to help subclasses, but were never implements. > To dig a bit deeper I decided to setup my simple system to work under Apache > 1.3.x and Apache::Registry to see what is going on with _url_cache when > mod_perl is being used. I found that the PARAMS is present but empty and > that is it. > > I have not tested with pure mod_perl yet but it would seem that the caching > system needs some changes or rethinking. It is quite possible I might be > missing something, so please enlighten me if that is the case. Yeah, the URL caching does probably need some more thought. Although it does work under mod_perl. If you have any ideas on how this could be re-done, or patches to make it work under FCGI, then I'm definitely willing to help get that done so it works for you crazy FCGI folks :) -- Michael Peters Developer Plus Three, LP --------------------------------------------------------------------- Web Archive: http://www.mail-archive.com/[email protected]/ http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2 To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
