Setup a single appRequestHandler() that uses a hash table to map uris to
functions. Becomes even more useful when you put your library code for
sessions, headers, footers, etc in the wrapper routine.
---------------------------------------------
my $info = {
c jon larsen => 'richweb.com',
email: => '[EMAIL PROTECTED]',
wireless: => '+804.307.6939',
};
On Fri, 31 Mar 2000, Shevek wrote:
> On Fri, 31 Mar 2000, Vivek Khera wrote:
>
> > My question to all of you who use handlers directly, how do you manage
> > all your handler mappings? I've seen it done where you add a
> > <Location> mapping for each handler you use, which corresponds to each
> > "program" you need. This, in my experience, tends to be error prone
> > and results in much cruft in your httpd.conf file.
>
> I have a single handler which matches all files, if the file exists
> ($r->finfo and other tests), it returns DECLINED. Else it makes a decision
> in Perl, and dispatches to the relevant handler in Perl. This makes
> loading the Perl script in a server very intensive, a problem which I am
> looking to solve soon.
>
> Ta.
>
> S.
>
> --
> Shevek
> GM/CS/MU -d+ H+>++ s+: !g p2 au0 !a w+++ v-(---) C++++$ UL++++$ UB+
> US+++$ UI+++$ P++>++++ L++++$ 3+ E--- N K- !W(-----) M(-) !V -po+ Y+
> t+ 5++ !j !R G' !tv b+++ D++ B--- e+ u+* h++ f? r++ n---- y?
> Recent UH+>++ UO+ UC++ U?+++ UV++ and collecting.
>
>
