in reply to Re: Apache2 Frustrations
in thread Apache2 Frustrations

This is a completely new web app, so would you recommend using modperl 1.x right now, then migrating to MP2 when it comes out?

------
We are the carpenters and bricklayers of the Information Age.

The idea is a little like C++ templates, except not quite so brain-meltingly complicated. -- TheDamian, Exegesis 6

... strings and arrays will suffice. As they are easily available as native data types in any sane language, ... - blokhead, speaking on evolutionary algorithms

Please remember that I'm crufty and crochety. All opinions are purely mine and all code is untested, unless otherwise specified.

Replies are listed 'Best First'.
Re: Re: Re: Apache2 Frustrations
by Arunbear (Prior) on Nov 21, 2003 at 22:01 UTC
    modperl 1.x will be around for a long time. It makes a lot of sense to use that now and migrate to version 2 when the latter has stabilised :)
Re: Re: Re: Apache2 Frustrations
by !1 (Hermit) on Nov 21, 2003 at 22:26 UTC

    Yes, I am telling you to wait for the time being and instead go with mod_perl 1.x. If you take a gander at the API documentation and run through some of the modules, you might notice that some of them are less than complete. I'm not saying that I dislike MP2 at this point. I'm saying that in order to get a feel for the entire API you either have to read an assload of source code or pay 99 cents a minute talking to the Psychic Friends Network getting yes/no/vaguely detailed answers to API questions (pricey, but definitely very entertaining...I never knew that APR::Table had a spirit that wishes for me to release it. No lies. Ask antirice). I'm certainly excited about MP2. I like the control that Apache 2.0 seems to offer. Unfortunately, it just isn't there yet. I have a couple of document servers running on our intranet with Apache 2 using a mod_perl handler to check for authentication and whatnot in an attempt to get a feel for the new way of doing everything (ok, not everything but things like args parsing in list context(ok, multi value didn't work) doesn't work the same and send_cgi_header is gone). I've already started to develop libraries (mostly by stealing chunks from CGI.pm) that work outside of Apache::compat however it's mostly a side project. It'll have to wait until antirice and I finish with our HTML::Template extension modules.