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).
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
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:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, 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, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.