"[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
> 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).
I'm just saying that APR is not the easiest bitch to handle on this
planet... And I've given my full support since it seems that you guys want
to refactor the JK api and use APR... Since there is already a working
connector based on APR, and you're refactorying the JK API, I thought it
might have been wise to use the already working APR-ized connector as a
starting point. I don't mind rewriting the full WebApp core if it's worth
to, it doesn't scare me...
I'm just trying to be the nice guy around here, simply saying "part of it is
there, and if you guys want, I'm more than welcome to turn the sucker inside
out"... Trying to avoid duplicate work...
If that's against your way of working, well, I'm just going to go ahead my
own way. I simply thought that the one mentioned above was a win-win
situation...
But as always, if you don't want to, well, whatever :) We're just going to
go on and re-duplicate work over and over again... WebApp, as JServ, (and
3.3 for you?) is my baby, and I'm not going to abandon it, even if you guys
kick me out :)
I just said that if you want to APR-ize JK and change the API, well, maybe
we can see to lay the grounds for new foundations?
Pier
