|XP is just a number|
The fact that for certain infinite loops, such as the one created from the same script I've given in a commented post below, prevent you from ending the process (this only occurs on Win32, the same script under Linux can be killed), I hold ActiveState responcible.
This is an entirely incorrect supposition and one that could be tested by running a similarly malfunctioning CGI program written in any other language of your choice.
"firstly it assumes that all Perl programs are run under the CGI and need only to run for a short time" - Please point out EXACTLY where ANY of my statements make this assumption.
It is implicit in the assertion that some 'PerlTimeOut' configuration (with a default value of 60 seconds nonetheless) should be introduced into Perl, when you yourself state that the problem only occurs when running Perl CGI programs under IIS.
"failure on the part of the server administrators" So what are you saying. A administrator with more than 200 accounts on his server should manually vet, test and approve all CGI scripts that get uploaded to the server by a user? Plain ridiculous.
You obviously failed to read or understand the sentence where I said "it is the responsibility of the administrator to ensure that ( the IIS configuration is) set appropriately for the kind of use that the server will be put to" Couldn't be clearer. If the systems administrators of a hosting company are not compentent to do this then you are unlikey to want to use that company whether they offer Perl or not.
Perl knows when it's being calls from a web server be it apache or IIS, the timeout would only need apply in this case. Seemed to obvious to post, but I guess some people need to be told.
I'm sure when you have worked out precisely how it is that perl 'knows' this then p5p will be more than happy to discuss your patch.