Storing config values in-memory between sessions

Hi, We run a script, server.cgi, running on a Apache2 instance using mod_perl support for 'older' CGI scripts. server.cgi is called by multiple individual clients at a time, returning an XML. It contains some config values that change from time to time (once a week) e.g, campaign end date As it

Re: libxslt read file rights problems on debian Lenny under mod perl 2.0

Petr Pajas wrote: Is there another web application running on your apache web server that is using libxslt (directly or indirectly via some other library)? No, I'm running just one web app. I can probably try to run a really small test case in a mod_perl handler, without loading my entire app

Re: Handler Chain (based on request method)

On Wed, Oct 28, 2009 at 12:58 PM, Aaron Dalton wrote: > I'm using mod_perl and CGI::Application::Dispatch to create a RESTful > web application.  In the one resource, GETs should be sent to the > default handler, and all other requests to the dispatcher.  I have tried > using and , but they do no

Re: Handler Chain (based on request method)

André Warnier wrote: Just by curiosity, what happened to the suggestions I gave you on the Apache httpd list (apart from the first one, which was to cross-post here) ? Ok, sorry, I see that response to the httpd list just got there. Maybe better to move the whole discussion here, there is p

Re: Handler Chain (based on request method)

Aaron Dalton wrote: I'm using mod_perl and CGI::Application::Dispatch to create a RESTful web application. In the one resource, GETs should be sent to the default handler, and all other requests to the dispatcher. I have tried using and , but they do not appear to be working. The handlers get

Handler Chain (based on request method)

I'm using mod_perl and CGI::Application::Dispatch to create a RESTful web application. In the one resource, GETs should be sent to the default handler, and all other requests to the dispatcher. I have tried using and , but they do not appear to be working. The handlers get processed regardless.

Re: mod-perl child process

On Wed, Oct 28, 2009 at 12:32 AM, Kulasekaran, Raja wrote: > So, How to I control this ?. Is it possible to reuse the existing > connection ?. It should be doing that already. Each process will open one connection and keep it open (unless you use different connection parameters, like a different

libxslt read file rights problems on debian Lenny under mod perl 2.0

Hi everyone, I'm experiencing a rather interesting problem after migrating one of our web applications to debian lenny. We have xml+xslt based web rendering, and we use XML::LibXSLT (currently on Lenny, 0.66), to do this. After migrating to Lenny, XML::LibXSLT refuses to read in and parse any s