I've been looking into this myself. Why are there no multi-thread Perl-centric application servers (ala Java's Tomcat) ?
mod_perl is not a realistic option for me because some of our customers use IIS / ISA proxy server.
What would be ideal is a standalone multi-thread webserver written in Perl that could be reverse-proxied using Apache or IIS/Proxy Server. I want to avoid the startup overhead of CGI, and the non-portability of mod_perl. Having a standalone HTTP app server that's proxied seems to be the way to build scalable web apps.
At least according to these guys...
The web is a pipe
fastcgi-scgi-and-apache-background-and-future
Is building a light-weight multi-threaded web-server in perl really that hard ?

---

---

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