in reply to Re^3: What filehandle should be used for HTML prints via CGI??
in thread What filehandle should be used for HTML prints via CGI??
fork? That's not how processes happen to come to life in Windows (at least most of the time, the perl fork() builtin included!) which is in all likelihood what PockMonk uses. In either case even under Windows is is the process that starts another process who decides where do the STDOUT, STDERR and STDIN point to (if anywhere at all). In case of a process started by the cmd.exe (the "command line" or "command prompt" or "shell" (for the unix folk)) then the STDOUT and STDERR point to whereever cmd.exe needs them to to display them in its window. In case of CGI scripts, they point to whereever the web server needs them to point to so that it can process the stuff a bit and forward it to the browser.
Though definitely no fork()s and no TTYs are involved. The whole world doesn't run Unix Fletch.
|
|---|