Ok. Thought I should clarify a few things.

This isn't a problem I'm having with my hosting company. I have my own dedicated server, which I manage well without trouble.

I sell commercial CGI scripts.

In my 5 years experience selling these scripts to customers with every kind of hosting company you can imagine, I have found that a growing number Win32 hosting companies are not installing Perl because of the problems mentioned in my first article.

Such companies are easy to find, just search for "windows hosting php asp -cgi". Google returns 1,520,000 results.

This is a number which keeps on growing. In my view Perl has the capability to be the most popular multi platform scripting language in the world. If it weren't for this fixable issue there would be no reason for Win32 hosts not to have Perl.

Recent polls show that PHP and ASP are now more popular than Perl for internet applications.

All because of this issue, which has been the same issue for 5 years. Why is the Perl community which I am a part of letting this happen. Why isn't anything being done?????

I'm now fed up with this problems existance, and I'm taking it upon myself to make sure it is sorted.

C, or Python, or Scheme, or Fortran, or INTERCAL are not commonly used for internet apps at all. For similar or the same reason.

I'm not saying Perl should never run for more than a fixed number of seconds. Of course perl scripts should do this. But when perl is launched from Apache or IIS it should have a set timeout. One that can't be broken by the users hitting his stop or refresh button.

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.