Oh, please, the histrionics aren't amusing any more.
Thirty seconds with google looking for, say, IIS cpu time limit pulls up plenty of stuff. Like docs for the CGITimeout, CPUCGIEnabled, and CPULimitProcStop properties from Microsoft's knowledge base. Sure looks like IIS does all this already.
Patching perl won't fix this problem without a damned impressive patch. The ones you've proposed just won't work -- besides being undone by the first alarm set in the process, it won't catch all the cases where things run wild anyway.
It's possible that I have no clue here how webservers work, haven't been up to my elbows in perl 5's guts on several platforms, haven't been working on perl 6, and aren't the guy who'd have to design the bits that'd be needed to make something like this work in the future. And it's also possible that everbody who's commenting is utterly clueless here.
Or... not. Sometimes when everyone tells you you're wrong you actually are wrong.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
Outside of code tags, you may need to use entities for some characters:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||