Re: Separate fascgi server.

Andrew Velikoredchanin wrote:
> Marc Prewitt пишет:
> 
>> fastcgi doesn't use unix domain sockets to communicate between the 
>> webserver and app server.  Instead, it uses tcp/ip to communicate. 
>> Using the externalfastcgi application directive with apache you can 
>> even have the application on a different host than the web server.
> 
> 
> No-no-no!!!
> I want use full separate fastcgi server - without apache or ather httpd 
> server. This is need for use nginx httpd server. It not run fastcgi 
> server self. This need already runing fastcgi server.
> 

Ok, you can run a fastcgi application server without running apache but 
you need a process manager (mod_fastcgi has a built-in process manager). 
  There is a perl process manager available at:

http://www.cpan.org/modules/by-module/FCGI/

(FCGI-ProcManager-0.17.tar.gz)

You could build your own in any other language using the fastcgi libraries.

We built our own (for perl) but I don't remember why.  Maybe the other 
one wasn't available at the time.  However, we ended up not using it. 
Most of the nice things like stderr logging, child reaping, signal 
propogation are handled by mod_fastcgi, so even if we are going to 
separate the webserver from app server, we still use apache on the app 
server because it's easy to maintain.

However, you will still need a web server to handle the incoming 
requests which forwards them to the process manager.  So, if you are 
trying to use fastcgi without a web server entirely, the answer is no. 
That said, you could build your own process manager which also accepts 
incoming http requests and sends them to your fastcgi processes.  But at 
that point you've already built your own webserver/appserver so I'm not 
sure what you've saved yourself by using fastcgi.

___________________________________
fastcgi-developers mailing list
http://fastcgi.com/fastcgi-developers/