On 12/01/2010 02:16 PM, Joost van der Sluis wrote:
My FastCGI process is running as a windows service.
What is exactly the reason for this? Isn't it much easier when the
webserver starts (and stops, when it is not used) the cgi-application,
than doing this in a Windows service?
As creating process is a time consuming effort in Windows, fast-cgi-ing
already running processes would offer a lot faster response.
OTOH, If doing Windows, Microsoft of course wants you to use IIS.
Microsoft IIS provides the ISAPI interface between the webserver and the
cgi program, that in this case is neither a program nor a service, but a
DLL. ISAPI offers similar features like FGCI but in a Windows-centric way.
A colleague of mine (using Delphi) did a quite complex application based
on ISAP. it's running just fine for a lot of customers.
In fact he did an ISAPI "proxy" DLL, that communicates with a service
(or program). This way debugging is a lot easier than directly debugging
the ISAPI DLL.
-Michael
--
_______________________________________________
Lazarus mailing list
[email protected]
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
