Re: getting started questions
joe-QzMH92Wc/[email protected]
| Newsgroups | gmane.comp.web.fastcgi.devel,gmane.spam.detected |
|---|---|
| Message-ID | <[email protected]> |
On Aug 16, 2007, at 21:38 UTC, joe-QzMH92Wc/[email protected] wrote: > Is it possible to set up Apache's mod_fastcgi to always use TCP > sockets, even on the local machine? Just to follow up on my own question here... I've found the -port option for the FastCgiServer directive. So if I specify -port 5000, then my FastCGI app should listen for an incoming connection on port 5000, right? Or, if I use the FastCgiExternalServer directive, then there is a -host (hostname:port) option which seems equivalent. This is documented as the host and port that "the application uses for communication with the web server," which seems backwards to me. Shouldn't it be the host that the FastCGI application is running on? Do I understand correctly that the FastCGI app should be listening, and it's the web server (via mod_fastcgi) which is initiating the connection? One final question on FastCgiExternalServer, if you'll bear with me. It sounds like this lets me launch my FastCGI app myself however I like, including under the debugger. If so, that will be a huge boon for development; I should be able to develop & debug this way, and then switch to the FastCgiServer for deployment. Is that right? Thanks, - Joe -- Joe Strout -- joe-QzMH92Wc/[email protected] Strout Custom Solutions, LLC ___________________________________ fastcgi-developers mailing list http://fastcgi.com/fastcgi-developers/