"Gomez Henri" <[EMAIL PROTECTED]> wrote:
> I'm ok for that, may be by merging ajp14 and warp (ajp20).
Ok... I can agree with that...
> We could have this protocol implementation in mod_jk
> and mod_webapp :)
Sure do...
> I'm serious here...
Me too...
> - with mod_jk, you'll gain AP1.3/AP2.0/IIS/NES/IPLANET/DOMINO,
> fault-tolerance, load-balancing, JNI and a good old and known modules.
Yeah...
> - with mod_webapp, you're right on the future with goodies like APR.
> And may be tomcat 4.0 could also add ajp13 support from works in JTC ?
Ok... I have no clue on how JK works, but fairly know how to take the shit
out on TC side... I'll give a shot to JK and AJPv13, run watchdog and
tester, at the same time, I'd like for you to look at WebApp and tell me
what's wrong with it...
Why don't we keep a NON-APR (JK), and progress works on APR based on WebApp?
Joining AJPv14 and WARP?
> The best of both world....
Definitely...
> PS: Something goes crasy these days, on tomcat list, what do you think about
> this Pier (known as my worst enemy :)
I believe it's because we are all so tired about fighting, and going out
with the two trees (3.3 and 4.0) more or less at the same time, offloaded
the pressure _a_lot_... And we don't want to be bitchy with each other?
Pier (feeling awkward!)
