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.
When you finally do decide to migrate, it's not that hard, and you'll
be in good company.
Rob
On Thu, 18 Nov 2004 12:00:58 -0500, Michael Peters
<mpeters@xxxxxxxxxxxxx> 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 move to apache2? I know from recent discussions that
> > CAP::apache::stuff is tough enough moving to apache 1.x, so presumably
> > apache2 support is further off?
>
> Are you planning on doing development under mod_perl or vanilla cgi?
>
> As far as I know, vanilla cgi should work just fine under apache2. I
> haven't verified that CAP::Apache works under mod_perl2 (apahce2) but I
> don't imagine it would be that difficult to make sure it does. Support
> could be added quickly especially if there is interest :)
>
> --
> Michael Peters
> Developer
> Plus Three, LP
>
>
>
>
> ---------------------------------------------------------------------
> Web Archive: http://www.mail-archive.com/cgiapp@xxxxxxxxxxxxxxxxx/
> http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2
> To unsubscribe, e-mail: cgiapp-unsubscribe@xxxxxxxxxxxxxxxxx
> For additional commands, e-mail: cgiapp-help@xxxxxxxxxxxxxxxxx
>
>
---------------------------------------------------------------------
Web Archive: http://www.mail-archive.com/cgiapp@xxxxxxxxxxxxxxxxx/
http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2
To unsubscribe, e-mail: cgiapp-unsubscribe@xxxxxxxxxxxxxxxxx
For additional commands, e-mail: cgiapp-help@xxxxxxxxxxxxxxxxx
|
Try Searching:
servers, voip, java, networking, microsoft ...
|
|
|
|