>>> Stas Bekman writes:
sb> Luckily Matt has got sick of waiting for someone to work on the
sb> advocacy of mod_perl and he has just taken over it. Having a
sb> good informational site is good, but it's not enough. We need to
sb> solve the problem of people to find this site and wanting to use
sb> mod_perl. Solution? Spreading the word.
i agree with what SB says, spreading the word is of primary
importance.
additionally, i think that some consideration should be given to
how mod_perl is packaged. although it's well documented (and
generally quite simple) there are three kits that need to be
compiled (apache, perl, mod_perl) before the simplest handler
can be tested. i think to an applications programmer who's
perhaps written a few CGI scripts, setting up the infrastructure
necessary to run mod_perl is a bit daunting, particularly if it
also involves mod_ssl.
this is the biggest complaint i've heard from new users, and i'm
not certain that i have any viable solutions to offer; after
all, there's gobs of documentation already, thanks to the guide.
perhaps bundling the various components together and driving the
configuration/build from a single script? i don't know.
cheers,
k.
--
kevin montuori
support independent booksellers -- http://www.booksense.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
