I guess those of us who are using PM every day get used to the delays. However, one comment I have had from friends and colleagues is how slow the response is. At that point, I would explain about the nature of CGI, and make out that the application has to do quite some work before it displays a page ... excuses, excuses.

I don't think this is doing the reputation of Perl any good, as a web application language - IMO it's time this was addressed.

Before replying to this post, I decided to download the Everything engine, just to take a look for myself. One of the pieces of advice that monks are meteing out on SoPW regularly, when CGI apps are slow, is to consider ModPerl.

Has anybody thought about, or even got working, an Everything Engine on ModPerl? From a cursory inspection, it does not look too bad, as the CGI code itself seems to be localized into the module html.pm.

By the way, I am interested in PM Dev as well. Not sure how much time I can give (possible issues with PHBs and circular tuits).

---

---

• 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.