Yes that's what I'm saying. IIS opens perl, but it's perl that actually takes down the server. Hosting companies don't care who's to blame, or who fixes the problem as long as then don't have to lift a finger. They just care right now that the problem exists, and they are avoiding perl because of it. If you give people guns you should monitor where they shoot them. Is this the American "If everyone has a gun, no one will get shot" theory coming out. If your going to give people guns (perl) then you should stop them from killing people (taking down server).
in reply to Re^3: a few clarifications
in thread Win32 Hosting companies not supporting Perl
A similar problem exists with apache, as long as the user clicks there stop button.
Microsoft are never going to fix the problem. So the Perl community will have to. I'm happy enough to develop a solution myself. But I would need a little help as I don't know where in Perl I would need to make changes, or even where to submit. I guess P5P.