On Fri, Jun 29, 2001 at 06:38:34PM -0700, [EMAIL PROTECTED] wrote:
> Please don't take this personally - I put some (free) time into
> this, and if I don't like your solution doesn't mean I consider you an
> "idiot" ( or that I'll not use the same solution, as it's considerably
> easier to implement :-)
>
> I spent a whole night reading the mod_webapp sources and trying to
> understand how this magic autoconfiguration works. There is a big interest
> in simpler configuration for apache+tomcat, and your code was the first
> place to look for something that can be merged into mod_jk.
One thing that mod_webapp has going for it is that it is based on APR
(this makes the webapp code much simpler). In my experience with
mod_jk, I've always had problems getting the right defines for my
platform (as there is no configure script - somehow, I remember J.F.
Clere adding some stuff to j-t-c). But, I think that for native
platform code, you'll get a big win by using APR.
The problem with APR is that you need to have a coherent strategy for
using it. APR works, but it is still rough (esp. with "installed"
APR). As discussed on dev@apr (think tomcat-dev was CCed), the two
main projects that use APR (Subversion and httpd-2.0) both rely on
the source - not the installed version of APR. Not to say that using
the installed version is impossible, but just that no one else has
really done this yet.
I just ran into a problem with mod_jk from TC 3.2 where it wasn't
dealing with the socket code correctly (this was fixed in 3.2.2, FWIW).
It just seems that APR could allow the j-t-c folks to not worry about
some lower-level stuff AND you get immediate cross-platform
functionality of any code that you write. IMHO, that can't be
underestimated. Let APR handle all of the odd OS stuff and focus on
what it is that you are trying to do. You'll end up with better code
all around.
My $.02 as an APR zealot. -- justin
