httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Randy Terbush <>
Subject Re: ScriptAlias-like extensions for perl etc
Date Fri, 26 Apr 1996 21:22:20 GMT
On this same topic, you may also want to take a look at a Perl5
module called the "Event" module if I remember correctly. Offers
the ability to preload perl functions and execute them based on
a received event.

I've glanced at this for the same reason but have never worked
it up my priority list.

You'll find it at CPAN.

> > What you *really* want is to design a protocol for sending CGI data
> > (possibly with some extensions) over a socket to a coopertating daemon.
> > 
> > That way you can write server co-daemons.  No exec'ing!!
> I'm missing something. If you have a CGI daemon (say for perl) sitting
> waiting for requests, then it'll need to fork children to process each
> request (unless you queue them - hmm, yuck). But you do save on the
> initial perl startup/parsing.
> > mod_perl is ok for perl stuff but co-daemons would solve the problem
> > in a generic fashion.
> > 
> > Hope this inspires someone :-)
> At first glance, from a perl prespective this doesn't sound too
> complicated. Let's get a feel for what's needed;
> Talking to a perl daemon Apache needs a way to send environment
> variables to give to the 'CGI script'. If (as I suspect) env vars
> can't contain line feeds, then they can be sent in a HTTP-header-like
> way
> PATH_INFO: /foo/bar
> SCRIPT_NAME: finder
> here's the POST data
> All the perl CGI scripts can be made into subroutines so that they're
> pre-'compiled'.
> Hmmmm. Maybe I should have a stab at that this weekend.
> Before I do, I'm pretty sure that someone mentioned a prototype
> along these lines. Was it called a CGI-pipe?
> rob

View raw message