On Fri, 14 Sep 2001, Pier Fumagalli wrote:
> At the same time, since also JK is moving towards APR, but they're far
> behind what WebApp does ATM, let's try to refine/update/change the WebApp
> API, already based on APR, and work on it as the APR based connector, when
> that is ready, we can think about porting all nice stuff that are still
> missing (load balancing, JNI and such), over to the new architecture...
Pier, APR is a library of portable code - not a new 'architecture'. Mod_jk
has an API that is used with 4 different protocols ( webapp will be the
5th ), 4 different web servers. This architecture is pretty well tested
and stable.
I'm not sure I understand your idea - of moving all this into webapp,
instead of moving warp as a jk protocol ( or integrate it with ajp14).
Costin
>
>
> So, IMO, it's a win-win situation... JK can support all web-servers and all
> "old" protocols, it's tested, it works, we just need to make it able to talk
> the new "AJPv14/WARP" protocol and can be used as the "strong" foundation.
> WebApp will talk only "AJPv14/WARP", based on APR, and only ported to Apache
> 1.3 and 2.0, when we're happy with it, with the 3.3 implementation of
> "AJPv14/WARP", with the new/revised/corrected APR-based API, we can start
> porting all other stuff over, and in 12 years time we can deprecate the old
> one...
>
> Does it make any sense?
>
> > As usual I'm also pondering why I'm spending so much time on IIS and
> > Domino when I wouldn't run anything apart from Apache if I ruled the
> > world. I wonder what I did in a past life...
>
> :)
>
> Pier
>
