> > I'm concerned that six (or eighteen) months down the line if I have > > questions they'll be answered by "you should be running the most > > current version, stop pestering with obsolete Apache 1.3" Setting up > > a new server has been enough of a pain without doing it again in a > > few months. > > I suppose that's possible, but I find it unlikely. Apache 1.3 is very > stable and I don't expect to see a mass shift to Apache 2 in > production usage any time soon, particularly in mod_perl programming > where the porting costs are non-zero. > > Actually, considering the relative pace of Apache 2 versus Apache 1.3 > development, I think you're more likely to encounter the situation you > fear with Apache 2. The chances of a major new release altering > significant functionality in Apache 1.3 is quite low. > > -sam
Sam, This opens an interesting debate as tomcat/mod_jk2 has similar issues, and there development and the user community seem more focused on 2 than 1.3. This makes 2 more attractive. I also get the feeling that module development seems to have more activity around 2 in other areas. Obviously MP is allot different, but one day I think we would want MP to be a better choice on 2 than 1, and I get the impression the HTTP developers are moving on to 2, and view 1 as legacy. AIMHO of course. Greg -- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
