comment on

The main advantage is that there is no cgi interface and no dependency on Apache (as the system is up all the time, there is no compile problem and no mod_perl complication).

Hmmm, how is not having a CGI interface an advantage? You certainly don't want to use the CGI interface for anything that has to be fast, but it's still nice to have one for legacy scripts. What is this compile problem and mod_perl complication you speak of?

The main dissadvantage is that all the details (ssl handling, authentication, authorisation, etc) have to be worked out through the application logic or through a proxy, and that since there is no cgi interface, all queries need to structures like a branch, with only the leaf being free text and the branch nodes being predermined.

It looks to me like you would have saved a lot of effort by using mod_perl (or FastCGI or PersistentPerl).

In reply to Re: multithreaded web application server in perl by perrin
in thread multithreaded web application server in perl by hackmare

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.


Clear questions and runnable code get the best and fastest answer
	PerlMonks