I use Apache and mod_perl for the server side apps.
I wouldn't use HTTP::Daemon on the server side, because
it is slow and doesn't have the administration features
that I really need.
One of our apps needed a little web server on the desktop,
so for that we used HTTP::Daemon. This allows us to
deploy a simple, more portable configuration to a
large number of users. It's multiplatform, also.
The biggest difficulty with Apache is the learning curve
for doing complicated things.
Apache tries to make simple things simple. Like
just about everything else, it's not quite as good
as perl in this regard.
Apache has a modular architecture and can be built
for low resource usage. 750K for an httpd process
is not unusual. For CPU usage apache should be much
lower.
It should work perfectly the first time! - toma
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.