Perhaps I just don't undestand how infrequently Apache and Tomcat get used together.
I was under the impression (perhaps incorrectly) that they get used together often enough to warrant the plugin's inclusion with the Apache source code. (After all, both projects *are* ASF projects.) But it's perfectly possible that I, and all the web developers I've worked with over the years, are not an accurrate representation of the Apache user base as a whole. If the module is not included as a part of Apache, and instead ships with Tomcat, it would sadden me and many web developers I know, but, Andre, as you point out, there are good reasons for your line of thinking. -Manni -----Original Message----- From: Andr� Malo [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 20, 2004 1:59 PM To: [EMAIL PROTECTED] Subject: Re: Invitation to HTTPD commiters in tomcat-dev * "Manni Wood" <[EMAIL PROTECTED]> wrote: > > > Having proxy_ajp included in httpd v2.0 would be a good thing - there is > > > a base of users for it (with it's more advanced handling of things like > > > indicating secure connections, etc it's useful). > > > Hmm. I'd include rather in tomcat distribution than httpd-2.0. That seems > > to be way more logical. > > I'd include it in Apache, not Tomcat. > > It's an apache module, after all, oh? Like all the other hundreds of modules out there? mod_perl? mod_python? Sorry, that's not an argument. nd -- Gefunden auf einer "Webdesigner"-Seite: > Programmierung in HTML, XML, WML, CGI, FLASH < # Andr� Malo # http://pub.perlig.de/ #
