On Fri, 14 Sep 2001, jean-frederic clere wrote:
> > >Maybe to you, but buddy "Costin" doesn't like it... :)
> >
> > No I'm sure Costin like the merge, and I like
> > you all comment the following timing :
I like the merge, I don't like the idea of moving all jk features
over to webapp ( and not on the argument that APR is so difficult
that it makes more sense to do that then using APR in jk and adding
webapp's features ).
> 1) Release TC 3.3/4.0
>
> 2) Start to think on how to merge AJP14/WARP
>
> 3) APRise mod_jk (Adding in a sense you can have a code with/without it via
> configure would be a lot more work).
>
> 4) Add the AJP14-WARP protocol to mod_jk and mod_webapp (adaptation)
+1 - that seems a good plan, and we should do it anyway. The result would
be some common code we can share.
> 5) Add the worker concept to mod_webapp
+0 on this - with some changes mod_webapp could support all jk
workers, but I'm not sure what would be the use to duplicate.
We can call the result mod_jk_webapp - and will certainly include
all mod_webapp features, but I believe it's much easier ( and better )
to add warp to apr to jk ( rather then add workers, connectors, etc to
webapp ). And we can do that with minimal impact on jk stability.
Costin
