Daniel W. Burke wrote:
> We have an application we're serving by using the same
> set of source code, and setting up different
> sections in the virtual host to set different variables
> and path aliases based on who the customer is...
...
> What I'd like to do (if even possible!), is have someth
>
> what I'm hoping to be able to do should only have to load the
> settings once (the first time a request comes in for that location)
> for each process, so I'm not too concerned about database access..
>
> The main question I need answered first is, is this even possible?
IIRC, Jay Lawrenc
On Mon, 15 Apr 2002, Steven Lembark wrote:
> > Have a databae table that stores the information for each
> > setting, then load it dynamically as a request comes in...
> > mailer dream code:
> >
> > $ENV{REQUEST_URI} =~ /^\/(.*?)\//;
> > $base_path = $1;
> > if (!exists($Location{$base_path})) {
> Have a databae table that stores the information for each
> setting, then load it dynamically as a request comes in...
> mailer dream code:
>
> $ENV{REQUEST_URI} =~ /^\/(.*?)\//;
> $base_path = $1;
> if (!exists($Location{$base_path})) {
> ... do database calls to load necessairy informat
I'm wondering if this is possible at all, and if so, how
to accomplish it...
We have an application we're serving by using the same
set of source code, and setting up different
sections in the virtual host to set different variables
and path aliases based on who the customer is...
But we have