OK, thanks, got it working. Please correct me, if I am wrong, but this approach makes developing and debugging harder, because it is httpd which spawns the application, so to effectively kill the app and replace it with new build I have to restart the httpd (at least with lighttpd which I tested).
I see possible resulutions: 1. Create the application as a standard CGI and convert it to FCGI on deployment or 2. Make TCustomFCGIApplication's descendant and replace WaitForRequest with own code which binds, listens and accepts connections from httpd. Then, upon compilation, I need only to restart my application. Am I right? Dnia 10 lipca 2009 12:33 Joost van der Sluis <jo...@cnoc.nl> napisał(a): > Someone here said it didn't work on windows, but I think that's fixed in > the mean time. Linux should work, further I didn't test. > Fcgi indeed uses sockets for the communication with the web-server, but > for convenience stdin is used. For a real explanation see here: > http://www.fastcgi.com/drupal/node/6?q=node/22#S2.2 _______________________________________________ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
