Off-topic, but I am about to install an apache webserver on one of our
machines as a development machine. To a person who does not do web
development on a regular basis, but only on an as-needed basis, is
there a reason to move to apache2? I know from recent discussions that
On Nov 18, 2004, at 12:00 PM, Michael Peters wrote:
Sean Davis wrote:
Off-topic, but I am about to install an apache webserver on one of
our machines as a development machine. To a person who does not do
web development on a regular basis, but only on an as-needed basis,
is there a reason to
Cees Hek wrote:
On Tue, 16 Nov 2004 17:10:08 -0500, Jesse Erlbaum [EMAIL PROTECTED] wrote:
Performance benefits over Apache::Registry seem marginal when you
consider the total request time (network transit, database access, etc.)
OTOH, functionality takes a hit, as you are now seeing.
Also, if
On Thu, 18 Nov 2004, Rob Kinyon wrote:
Personally, I'd stick w/Apache1 for now. I just came off a project
where we decided to use AP2 and got bit by the fact that not all the
MP1 methods are implemented in MP2, such as what's needed for
Apache::SizeLimit. MP1 is battle-tested - I'd stick with it.
On Thu, 18 Nov 2004, Michael Peters wrote:
As far as I know, vanilla cgi should work just fine under apache2.
Mostly, yes. But some defaults are different, which can produce
maddening results:
http://use.perl.org/~samtregar/journal/11882
Now, that was more than a year ago, so maybe this is
Hi Michael --
+ speed - yes I know that in some circumstances CGI doesn't
perform that
badly under mod_perl since it doesn't need to be loaded again. I also
know that a web application typically has other bottle necks besides
parameter parsing and cookie generation (like database
On Thu, 18 Nov 2004 16:30:22 -0500, Jesse Erlbaum [EMAIL PROTECTED] wrote:
And one more thing: If you develop in API space, you probably have to
restart Apache every time you make a change. Wouldn't it be infinitely
easier to be able to start Apache in a development mode which causes
Minor
