Re: FastCGI 2.0.0

Bill Snapper (
Mon, 07 Apr 1997 16:05:49 -0400

Message-Id: <>
Date: Mon, 07 Apr 1997 16:05:49 -0400
From: Bill Snapper <>
To: Ben Gavin <>
Subject: Re: FastCGI 2.0.0

>  Yes, it does work.  Prints just as the program says, from the command
>prompt and from Netscape.  But when I run tiny-fcgi_nt.fcgi it invokes
>cgi-fcgi.exe (shows in Task Manager), and then just sits there.  I 
>don't get a no response message or anything from the browser.  And no 
>matter how many times I do it, it just spawns another instance of 
>cgi-fcgi.exe, it never reuses the old version.

Hmm.  Are your .fcgi text files in the same directory as the .exe
files that they describe?

FYI, the cgi-fcgi application should get launched for each new 
request.  This is by design.  The application's purpose is to provide
a bridge between any web server and a FastCGI application.  This is
obviously not the way to get good performance.  For that you need to
use a native FastCGI plugin for a Web Server.  This will however let
you have persistent applications (assuming that everything works).

One more thing to try.  Start your FastCGI application from a DOS
command prompt as follows:

cgi-fcgi -start -connect ?your_pipe_name? ?./yourApp.exe?


your_pipe_name is the name of the pipe specified in the .fcgi
               file.  For example "sockets_echo" from the
               echo_nt.fcgi file.

yourApp.exe is the name of the FastCGI application to launch.
              For example, ./echo.exe

If this is working, you should see your application up and running
after the command is executed.  If it is running, change the pipe
name to a port number like :8080 for example.  Then try and connect
to it using telnet.  See what happens.

Good luck.

- Bill -

Bill Snapper           | Open Market, Inc.   | My opinions are my own,
Software Engineer      | 245 First St.       | and not necessarily | Cambridge, MA 02142 | those of my employer, 
1-617-949-7365         |                     | Open Market Inc.