Hallo, Ruud!

*** Am Donnerstag 21. M„rz 1996 um 20:08 schrieb Ruud Senden an All:

 RS> Suppose I have a program which reads it's input from stdin, and sends it's
 RS> output to stdout. This program has to run permanently in the background on
 RS> a WWW-server. A CGI-script on the WWW-server should be able to send and
 RS> receive information to the permanent process (so the CGI-script should be
 RS> able to put information on stdin of the permanent process, and read
 RS> information from stdout of the permanent process).

If you know the exact CGI/1.1 specs you already have the answer. You need a
special wrapper like you suggested, which has to be started as a GGI
script. It is not possible for the WWW server to interface to a
"permanent"ly running program, since it waits for the CGI script
to finish and get its return code.

You will want to redirect stdin/stdout to pipes created with pipe() or
DosCreatePipe() (you need to create two pipes if you want to redirect both
input and output of the child), then save the current state of
stdin/stdout, DosDupHandle() the respective end of the two pipes to the
handle numbers associated with stdin/stdout (0/1), call the CGI script and
then restore the previous associations of stdin/stdout. The child should
notice eof(stdin) when you close the write end of the pipe that belongs to
its stdin.


Tschau...Thomas

--- E3-32/1.11-32/2.50+