On Wed, 1 Dec 2010, Michael Schnell wrote:
On 11/30/2010 02:52 PM, [email protected] wrote:
FastCgiExternalServer D:/counte/verbruik/server -host 127.0.0.1:2015
-idle-timeout 30 -flush
AFAIK, fastCGI can use as well a TCP/IP socket as a pipe to do the
communication between the WebServer and the CGI program (not really a big
difference regarding the program API).
Well, the TCP/IP port is passed to the FastCGI on standard input (using a
pipe) when it is started. All the other traffic is per TCP/IP. but as you
say, it does not matter from the Program API point of view, it's a matter
of configuration.
Michael.
--
_______________________________________________
Lazarus mailing list
[email protected]
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
