Martijn, > it would make sense to upgrade the software as well. So I upgraded > from Apache1 to Apache2, from mod_perl1 tot mod_perl2 and... well, I > think this meant I had not choice but to move to AxKit2 as well.
> 'AxKit2 does away with Apache', the wiki says. I have to admit that > this very statement puzzled me at first, as I had always though of > AxKit as just a mod_perl/Apache module but, if I understand correctly, > it is actually working alongside Apache, only taking care of (in our > case) the XML-to-XML-via-XSLT process? No, it has nothing to do with apache at all. It's a webserver in its own right. > Okay, that makes sense. But still, I'd like Apache and mod_perl to do > all the other things -serving images, pdfs, taking care of > authentication etc.- they have been doing so nicely for me all this > time. That probably is possible yes. (I haven't tried it tho). > But I am kind of confused about where to start. Or, since I > would like to keep using various existing AxKit plugins and taglibs, > is the whole idea to move to AxKit2 right now just not very clever? If you want to keep all that, either upgrade apache to 1.3.n and use axkit1 with mod_perl or go for apache2 with modperl2 and use, I believe, tomkit. > I apologise if this is a very low-level question. I will happily share > anything I learn by editing the wiki and, who knows, share new/changed > modules with the community. np! John --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
