More CGI Stuff

[Phil Davis]

----- Original Message ----- 
From: "David Bovill" <david.bovill at opn-technologies.com>
To: <metacard at lists.runrev.com>
Sent: Friday, August 30, 2002 11:33 AM
Subject: Re: More CGI Stuff


> On Fri, 2002-08-30 at 16:13, Yennie at aol.com wrote:
> > > 
> > Unfortunately, no- the server will spawn a new cgi process for each request.
> > I have found a couple options, however:
> > 
> > 1). Run a simple server which takes request from cgi scripts (over sockets), 
> > and supplies the persistent data.
> > 
> > 2) Run a pool of servers, all listening on their own port, and then still 
> > utilize 1).
> > 
> 
> With 2) is the idea to have the cgi script switch on each call to
> another process?
> 
> > I did cook up something fun to play with. I stuck this in a script "httpd" 
> > and call "./httpd 8080 10" from the terminal. What I get: 10 processes 
> > listening on ports 8080-8089.
> > 
> 
> Re: my recent post are you using 2.4.3 with httpd? Having problems with
> my server under 2.4.3...
> 
> In terms of IAC - which is what you are doing here right? Do you have
> any info regarding performance and the various techniques that are
> possible (in particular using an external, shell, and sockets)- what do
> you think:
> 
> 1) Shell (slowest)
> 
> 2) Sockets
> 
> 3) Externals (any faster?)
> 

FWIW, I believe Pierre Sahores explained a way to use PHP to manage sockets and enable backend use of MC as a long-running process. I think it's related to this thread. (Wherever that explanation is in the archives, maybe Ken Ray would consider adding it to his already excellent Developer Resources section at http://www.sonsothunder.com !)

Phil

> 
> _______________________________________________
> metacard mailing list
> metacard at lists.runrev.com
> http://lists.runrev.com/mailman/listinfo/metacard
>