Re: Deployment options
Chris Lightfoot <[email protected]>
| Newsgroups | gmane.comp.web.fastcgi.devel |
|---|---|
| Message-ID | <FDA/[email protected]> |
On Fri, Jan 27, 2006 at 11:29:32AM -0800, Bill Moseley wrote: > On Fri, Jan 27, 2006 at 07:27:21PM +0000, Chris Lightfoot wrote: > > On Fri, Jan 27, 2006 at 11:25:12AM -0800, Bill Moseley wrote: > > > In static mode (FastCGIServer) there's a separate Process Manager > > > process that handles running the application. So any apache child > > > process contacts that single process manager which exec the > > > application as needed. Is that correct? > > > > > > And in Dynamic mode there's no process manager, so each apache child > > > manages the fastcgi application process(es). > > > > no -- there's one process manager process for the whole > > apache instance, which is spawned at startup: > > So the difference between static and dynamic is only if the > application processes are started as server startup or not? and that you don't need to specify them explicitly -- you can have a directory full of scripts, or all *.fcg scripts, or whatever, started as FastCGI servers. -- Space Food Hideous -- But It Costs A Lot (newspaper headline) ___________________________________ fastcgi-developers mailing list http://fastcgi.com/fastcgi-developers/