With the lateste version of ActiveState Perl and IIS 6.0 is CGI implemented as invocing a new process that reads compiles and executes the Perl code on each request of the CGI script? Or is does ActiveState implement a "in process" model that does not have to create a new process to handle the request.
A couple of clicks from the activestate homepage leads me to the ActivePerl Features List, which mentions support for ISAPI under Windows.
How does CGI handle 1000 request of a cgi script in say a two minute time span?
By spawning an external program 1000 times. (If you mean how _well_ does it handle it, then that has rather a lot to do with the hardware that its running on, it will handle it a lot better on a system with four AMD 64 processors then it would on the old P75 I have sitting under my desk at home).
What causes a CGI process to terminate?
The same thing that causes any process to terminate - typically the script hits an exit() statement or reaches the end of the file.
In reply to Re: Question on Web Server Usage and Perl
by dorward
in thread Question on Web Server Usage and Perl
by Anonymous Monk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |