You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by cm...@yahoo.com on 2001/09/10 22:23:59 UTC
Re: [VOTE] Removal of mod_jk for Apache 2.0 from jakarta-tomcat f
or Tomcat 3.3
On Mon, 10 Sep 2001, Pier Fumagalli wrote:
> "GOMEZ Henri" <hg...@slib.fr> wrote:
>
> > Ryan to became more than just a contributer :))))
>
> This is the third time we agree on something in less than 24 hours. This
> implies that either I'm getting old, or just plain silly...
Now, if you could agree on merging mod_webapp and mod_jk, that would be
something...
Costin
Re: [VOTE] Removal of mod_jk for Apache 2.0 from jakarta-tomcat f
or Tomcat 3.3
Posted by Pier Fumagalli <pi...@betaversion.org>.
"Ryan Bloom" <rb...@covalent.net> wrote:
> Well, I'm new to the list, but I like to veto things too. Somebody point me
> at something I can veto....... :-)
You can always veto your committer status... :) :) :)
Pier
Re: [VOTE] Removal of mod_jk for Apache 2.0 from jakarta-tomcat f or Tomcat 3.3
Posted by Ryan Bloom <rb...@covalent.net>.
On Monday 10 September 2001 16:15, Christopher Cain wrote:
> Gomez Henri wrote:
>
> [snip]
>
> > PS: Something goes crasy these days, on tomcat list, what do you think
> > about this Pier (known as my worst enemy :)
>
> Something is indeed a little bizarre on the list today, mon ami. Maybe
> because Craig isn't here to keep us in line =)
>
> a) There are now four key people seriously discussing a partial merge of
> mod_jk and mod_webapp
>
> b) Henri and Pier are agreeing on all sorts of things
>
> c) The 3.3 guys are congratulating the 4.0 guys and vice-versa
>
> d) There have been about 15 votes in last 24 hours
>
> e) _I'm_ the short-tempered one, for a change
>
> The only reason I know for sure that the world is still spinning is that
> Jon is still vetoing things ;-)
Well, I'm new to the list, but I like to veto things too. Somebody point me at
something I can veto....... :-)
Ryan
______________________________________________________________
Ryan Bloom rbb@apache.org
Covalent Technologies rbb@covalent.net
--------------------------------------------------------------
Re: [VOTE] Removal of mod_jk for Apache 2.0 from jakarta-tomcat f
or Tomcat 3.3
Posted by Pier Fumagalli <pi...@betaversion.org>.
"Christopher Cain" <cc...@mhsoftware.com> wrote:
> Something is indeed a little bizarre on the list today, mon ami. Maybe
> because Craig isn't here to keep us in line =)
No, I believe we have to thank Jon for that... I believe that raising
another flame war at this point made us all realize that probably we _could_
work together somehow... The releases are out/planned, a biiiiig relief
valve... We might not agree on ANYTHING, but....
> a) There are now four key people seriously discussing a partial merge of
> mod_jk and mod_webapp
Oh yes...
> b) Henri and Pier are agreeing on all sorts of things
Weirdest 24 hours ever (well, since me and Peter Donald got along, anyhow!)
> c) The 3.3 guys are congratulating the 4.0 guys and vice-versa
Well, a release 's a release :)
> d) There have been about 15 votes in last 24 hours
More than that
> e) _I'm_ the short-tempered one, for a change
No, you're not...
> The only reason I know for sure that the world is still spinning is that
> Jon is still vetoing things ;-)
Ah, that's NEVER going to change...
Pier
Re: [VOTE] Removal of mod_jk for Apache 2.0 from jakarta-tomcat f or Tomcat 3.3
Posted by Christopher Cain <cc...@mhsoftware.com>.
Gomez Henri wrote:
[snip]
> PS: Something goes crasy these days, on tomcat list, what do you think
> about this Pier (known as my worst enemy :)
Something is indeed a little bizarre on the list today, mon ami. Maybe
because Craig isn't here to keep us in line =)
a) There are now four key people seriously discussing a partial merge of
mod_jk and mod_webapp
b) Henri and Pier are agreeing on all sorts of things
c) The 3.3 guys are congratulating the 4.0 guys and vice-versa
d) There have been about 15 votes in last 24 hours
e) _I'm_ the short-tempered one, for a change
The only reason I know for sure that the world is still spinning is that
Jon is still vetoing things ;-)
- Christopher
/**
* Pleurez, pleurez, mes yeux, et fondez vous en eau!
* La moitié de ma vie a mis l'autre au tombeau.
* ---Corneille
*/
Re: [VOTE] Removal of mod_jk for Apache 2.0 from jakarta-tomcat f
or Tomcat 3.3
Posted by Costin Manolache <cm...@yahoo.com>.
On Mon, 2001-09-10 at 16:48, Pier Fumagalli wrote:
>
> Why don't we keep a NON-APR (JK), and progress works on APR based on WebApp?
> Joining AJPv14 and WARP?
The important thing in mod_jk is the modularity, the fact that it
supports multiple server adapters and multiple protocols. This part has
nothing ( or little ) to do with APR or ajp14 or warp - and it is the
part I absolutely want preserved ( and improved ).
I'm quite familiar with webapp ( it's allways important to know the
competition :-), wa_request is the only serious obstacle (IMHO ).
If you can merge the request representation ( and callbacks ) to use the
same names, the rest will fit perfectly.
Even in the current status, with part of jk using it's own portability
routines and webapp using apr, there is no other problem in putting them
togheter, except for implemeting the glue code needed to add any new
protocol in jk.
Regarding the module itself- things are reasonably similar.
Costin
Re: [VOTE] Removal of mod_jk for Apache 2.0 from jakarta-tomcat f
or Tomcat 3.3
Posted by Pier Fumagalli <pi...@betaversion.org>.
"Gomez Henri" <hg...@slib.fr> 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!)
Re: [VOTE] Removal of mod_jk for Apache 2.0 from jakarta-tomcat f or Tomcat 3.3
Posted by Gomez Henri <hg...@slib.fr>.
En réponse à cmanolache@yahoo.com:
> On Mon, 10 Sep 2001, Pier Fumagalli wrote:
>
> > "GOMEZ Henri" <hg...@slib.fr> wrote:
> >
> > > Ryan to became more than just a contributer :))))
> >
> > This is the third time we agree on something in less than 24 hours.
> This
> > implies that either I'm getting old, or just plain silly...
>
> Now, if you could agree on merging mod_webapp and mod_jk, that would
> be
> something...
I'm ok for that, may be by merging ajp14 and warp (ajp20).
We could have this protocol implementation in mod_jk
and mod_webapp :)
I'm serious here...
Benefits :
- 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.
- 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 ?
The best of both world....
PS: Something goes crasy these days, on tomcat list, what do you think about
this Pier (known as my worst enemy :)
-
Henri Gomez ___[_]____
EMAIL : hgomez@slib.fr (. .)
PGP KEY : 697ECEDD ...oOOo..(_)..oOOo...
PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6
Re: [VOTE] Removal of mod_jk for Apache 2.0 from jakarta-tomcat f
or Tomcat 3.3
Posted by Pier Fumagalli <pi...@betaversion.org>.
"Ryan Bloom" <rb...@covalent.net> wrote:
>> Slowwwwwww down... :) If mod_jk wants to start using APR, I believe we're
>> talking, otherwise, I'm done with cross-platform porting, I live it to Ryan
>
> Oh no you don't. I did the cross-platform stuff. I wrote APR to get awar
> from it.
Yeah, that's why I'm saying that I'm leaving (spelling mistake up above) to
you... APR is just great...
Pier
Re: [VOTE] Removal of mod_jk for Apache 2.0 from jakarta-tomcat f or Tomcat 3.3
Posted by Ryan Bloom <rb...@covalent.net>.
On Monday 10 September 2001 14:05, Pier Fumagalli wrote:
> "cmanolache@yahoo.com" <cm...@yahoo.com> wrote:
> > On Mon, 10 Sep 2001, Pier Fumagalli wrote:
> >> "GOMEZ Henri" <hg...@slib.fr> wrote:
> >>> Ryan to became more than just a contributer :))))
> >>
> >> This is the third time we agree on something in less than 24 hours. This
> >> implies that either I'm getting old, or just plain silly...
> >
> > Now, if you could agree on merging mod_webapp and mod_jk, that would be
> > something...
>
> Slowwwwwww down... :) If mod_jk wants to start using APR, I believe we're
> talking, otherwise, I'm done with cross-platform porting, I live it to Ryan
Oh no you don't. I did the cross-platform stuff. I wrote APR to get awar from it.
Ryan
______________________________________________________________
Ryan Bloom rbb@apache.org
Covalent Technologies rbb@covalent.net
--------------------------------------------------------------
Re: [VOTE] Removal of mod_jk for Apache 2.0 from jakarta-tomcat f or Tomcat 3.3
Posted by Gomez Henri <hg...@slib.fr>.
> I'm actually right now working on the thread locks for Windows, and
> then
> I
> am going to start agitating for an APR release. We should have APR
> 1.0
> out
> the door soon-ish. I am hoping to have it released sometime in the
> next
> month
> or two. :-)
That's the last objection to use APR instead of current native works
in jk (ie jk_pool).
As soon there will be an APR, release we could start mod_jk translation
to APR (and yes MANY MANY MANY code cleanup).
-
Henri Gomez ___[_]____
EMAIL : hgomez@slib.fr (. .)
PGP KEY : 697ECEDD ...oOOo..(_)..oOOo...
PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6
Does Jasper use the Context Classloader for Compiling JSP files?
Posted by Will England <wi...@mylanders.com>.
Greetings!
I know there are two (or three) different classpaths within Tomcat 3.2.
The question is, does Jasper, when compiling JSP files, use the Context
Classpath, which referrs to the WEB-INF/classes directory for that
specific JSP?
If not, how could I add the Context Classpath to the Jasper code?
Can someone point me to a breakdown of the classloading within Jasper
specifically? I've seen the classloading for Servlets, and that is all
kosher.
Thank you in advance for any tips, pointers, or direction.
Will
--
/~>'find `funny quote`': Command not found; humor not installed.
1986 Concours 72,xxx CDA #00046 COG AMA
Overland Park, KS will@mylanders.com PCS: 316-371-FOAD
http://will.mylanders.com/
Re: [VOTE] Removal of mod_jk for Apache 2.0 from jakarta-tomcat f or Tomcat 3.3
Posted by Ryan Bloom <rb...@covalent.net>.
On Monday 10 September 2001 15:22, Pier Fumagalli wrote:
> "Ryan Bloom" <rb...@covalent.net> wrote:
> >> MMAP is the other scary stuff in APR, the new code (without Ralph's
> >> libmm) it no more than one month old... I need it for load balancing,
> >> but I want to double check with the guys in CA next week and see what
> >> they tell me before publishing anything..
> >
> > Actually, MMAP has been in APR for a long time, it is just shared memory
> > that is new.
>
> My bad... :)
>
> > And, the shared memory code has been stressed in Apache for the
> > last month. Also the shared memory code is basically just the important
> > stuff from the MM library.
>
> My last status was 2 weeks ago when I last saw David, and he said "wait for
> a little longer still"... So, can I assume that "little longer" is over?
I think so. The problem back then, was that he needed APR to be available before
he could do anything with apr-util, but we were cleaning APR before trying to
clean apr-util, and it just didn't work. That was a BeOS-only problem though.
Ryan
______________________________________________________________
Ryan Bloom rbb@apache.org
Covalent Technologies rbb@covalent.net
--------------------------------------------------------------
Re: [VOTE] Removal of mod_jk for Apache 2.0 from jakarta-tomcat f
or Tomcat 3.3
Posted by Pier Fumagalli <pi...@betaversion.org>.
"Ryan Bloom" <rb...@covalent.net> wrote:
>
>> MMAP is the other scary stuff in APR, the new code (without Ralph's libmm)
>> it no more than one month old... I need it for load balancing, but I want
>> to double check with the guys in CA next week and see what they tell me
>> before publishing anything..
>
> Actually, MMAP has been in APR for a long time, it is just shared memory that
> is new.
My bad... :)
> And, the shared memory code has been stressed in Apache for the
> last month. Also the shared memory code is basically just the important
> stuff from the MM library.
My last status was 2 weeks ago when I last saw David, and he said "wait for
a little longer still"... So, can I assume that "little longer" is over?
>>> I'm actually right now working on the thread locks for Windows, and then
>>> I am going to start agitating for an APR release. We should have APR 1.0
>>> out the door soon-ish. I am hoping to have it released sometime in the
>>> next month or two. :-)
>>
>> Yah... We need that thread locking for Windows... :) At least I do :) :) :)
>
> Give me one or two hours, and I will commit it. :-)
I'll be asleep in two hours... I'm thru for today... :(
Pier
Re: [VOTE] Removal of mod_jk for Apache 2.0 from jakarta-tomcat f or Tomcat 3.3
Posted by Ryan Bloom <rb...@covalent.net>.
> MMAP is the other scary stuff in APR, the new code (without Ralph's libmm)
> it no more than one month old... I need it for load balancing, but I want
> to double check with the guys in CA next week and see what they tell me
> before publishing anything..
Actually, MMAP has been in APR for a long time, it is just shared memory that
is new. And, the shared memory code has been stressed in Apache for the
last month. Also the shared memory code is basically just the important stuff
from the MM library.
> > I'm actually right now working on the thread locks for Windows, and then
> > I am going to start agitating for an APR release. We should have APR 1.0
> > out the door soon-ish. I am hoping to have it released sometime in the
> > next month or two. :-)
>
> Yah... We need that thread locking for Windows... :) At least I do :) :) :)
Give me one or two hours, and I will commit it. :-)
Ryan
______________________________________________________________
Ryan Bloom rbb@apache.org
Covalent Technologies rbb@covalent.net
--------------------------------------------------------------
Re: [VOTE] Removal of mod_jk for Apache 2.0 from jakarta-tomcat f
or Tomcat 3.3
Posted by Costin Manolache <cm...@yahoo.com>.
On Mon, 2001-09-10 at 16:40, Pier Fumagalli wrote:
> >> A third one could be an API merger between the two... If you want
to talk
> >> about it...
> >
>
> No, I meant between JK and WebApp... :)
Well, webapp has a very nice protocol - it would be a great addition to
jni, ajp12, ajp13 and ajp14. And I think it has a lot in common with
ajp14 - so it can share lots of code.
I don't think it's that important how the bytes are packed in the
message, so a real merge between warp and ajp14 might work.
Regarding the general API in jk - we do plan a major refactoring anyway,
after we get something stable tagged ( not only for APR, there are few
other things we can improve in the general layout ). And all good things
from webapp will be wellcomed ( you like it or not :-)
Costin
Re: [VOTE] Removal of mod_jk for Apache 2.0 from jakarta-tomcat f
or Tomcat 3.3
Posted by Pier Fumagalli <pi...@betaversion.org>.
"cmanolache@yahoo.com" <cm...@yahoo.com> wrote:
> There is no question about APR stability or release-like quality. As long
> as APR people are not certain the API will not change and don't put the "1.0"
> label on it.
I have insider news on this (me and David Reid hang out pretty often
together, he taught me how to drink beer), and the API is _very_ stable on
the stuff used in WebApp...
>> A third one could be an API merger between the two... If you want to talk
>> about it...
>
> Between jk/common and apr ? I don't think so, jk was designed from
> beginning as a placeholder until APR is ready, based on the same APIs ( at
> that time - APR changed quite a bit in the last year ).
>
> I prefer the first solution ( with a transition period when both apr or
> the current code could be used ), but in the end the portability code in
> jk will be just removed.
No, I meant between JK and WebApp... :)
>> MMAP is the other scary stuff in APR, the new code (without Ralph's libmm)
>> it no more than one month old... I need it for load balancing, but I want to
>> double check with the guys in CA next week and see what they tell me before
>> publishing anything..
>
> Yes, load balancing, also for NIO, and also for faster communication in
> ajp14.
NIO is kinda cool if used in multi threaded applications... Dunno that much
about in multi process... Worth discussing...
Pier
Re: [VOTE] Removal of mod_jk for Apache 2.0 from jakarta-tomcat f
or Tomcat 3.3
Posted by cm...@yahoo.com.
On Mon, 10 Sep 2001, Pier Fumagalli wrote:
> >> Mod_jk will use APR - that's certain. The only question is when and how
> >> to do the transition without affecting the stability of the code. Having
> >> an APR1.0 out is one of the requirements - I don't think we can release
> >> mod_jk, even from j-t-c, with dependencies on un-released library.
>
> In its current status, APR is very stable for at least what has been used in
> WebApp, meaning memory, IO and few other stuff. I would love to use thread
> locking (new piece of code in there since two weeks) but it's still too
> early to use it....
There is no question about APR stability or release-like quality. As long
as APR people are not certain the API will not change and don't put the "1.0"
label on it.
> >> There are already 2 proposals for how to do that - one with preserving the
> >> current common as a temporary solution, until we make sure it works with
> >> IIS/NES, and the other with removing the common utils and hoping things
> >> will work with IIS/NES.
>
> A third one could be an API merger between the two... If you want to talk
> about it...
Between jk/common and apr ? I don't think so, jk was designed from
beginning as a placeholder until APR is ready, based on the same APIs ( at
that time - APR changed quite a bit in the last year ).
I prefer the first solution ( with a transition period when both apr or
the current code could be used ), but in the end the portability code in
jk will be just removed.
> >> Right now the APR/common is not the main itch - it'll become pretty soon,
> >> at least for me ( I need mmap for the new connector )
>
> MMAP is the other scary stuff in APR, the new code (without Ralph's libmm)
> it no more than one month old... I need it for load balancing, but I want to
> double check with the guys in CA next week and see what they tell me before
> publishing anything..
Yes, load balancing, also for NIO, and also for faster communication in
ajp14.
Costin
Re: [VOTE] Removal of mod_jk for Apache 2.0 from jakarta-tomcat f
or Tomcat 3.3
Posted by Pier Fumagalli <pi...@betaversion.org>.
"Ryan Bloom" <rb...@covalent.net> wrote:
> On Monday 10 September 2001 14:51, cmanolache@yahoo.com wrote:
>>
>> Mod_jk will use APR - that's certain. The only question is when and how
>> to do the transition without affecting the stability of the code. Having
>> an APR1.0 out is one of the requirements - I don't think we can release
>> mod_jk, even from j-t-c, with dependencies on un-released library.
In its current status, APR is very stable for at least what has been used in
WebApp, meaning memory, IO and few other stuff. I would love to use thread
locking (new piece of code in there since two weeks) but it's still too
early to use it....
>> There are already 2 proposals for how to do that - one with preserving the
>> current common as a temporary solution, until we make sure it works with
>> IIS/NES, and the other with removing the common utils and hoping things
>> will work with IIS/NES.
A third one could be an API merger between the two... If you want to talk
about it...
>> Right now the APR/common is not the main itch - it'll become pretty soon,
>> at least for me ( I need mmap for the new connector )
MMAP is the other scary stuff in APR, the new code (without Ralph's libmm)
it no more than one month old... I need it for load balancing, but I want to
double check with the guys in CA next week and see what they tell me before
publishing anything..
> I'm actually right now working on the thread locks for Windows, and then I
> am going to start agitating for an APR release. We should have APR 1.0 out
> the door soon-ish. I am hoping to have it released sometime in the next month
> or two. :-)
Yah... We need that thread locking for Windows... :) At least I do :) :) :)
Pier
Re: [VOTE] Removal of mod_jk for Apache 2.0 from jakarta-tomcat f
or Tomcat 3.3
Posted by cm...@yahoo.com.
On Mon, 10 Sep 2001, Ryan Bloom wrote:
> I'm actually right now working on the thread locks for Windows, and then I
> am going to start agitating for an APR release. We should have APR 1.0 out
> the door soon-ish. I am hoping to have it released sometime in the next month
> or two. :-)
That's great ! As soon as 3.3 is released I think we should try a
j-t-c/mod_jk release with the current code ( which is very close to the
main branch, but has a number of extra features like ajp14 and use of
SetHandler jakarta/servlet in addition to JkMount ). Since 4.0 will be out
as well, we should just make sure j-t-c/jk works with both releases.
After we tag ( and maybe branch for eventual bug fixes ), we should start
transitioning to APR, and with a bit of luck we can get another release
out when APR1.0 is released ( and by that time probably ajp14 and the new
jni connectors will be reasonably tested and stable ).
Costin
Re: [VOTE] Removal of mod_jk for Apache 2.0 from jakarta-tomcat f or Tomcat 3.3
Posted by Ryan Bloom <rb...@covalent.net>.
On Monday 10 September 2001 14:51, cmanolache@yahoo.com wrote:
> On Mon, 10 Sep 2001, Pier Fumagalli wrote:
> > >> This is the third time we agree on something in less than 24 hours.
> > >> This implies that either I'm getting old, or just plain silly...
> > >
> > > Now, if you could agree on merging mod_webapp and mod_jk, that would be
> > > something...
> >
> > Slowwwwwww down... :) If mod_jk wants to start using APR, I believe we're
> > talking, otherwise, I'm done with cross-platform porting, I live it to
> > Ryan
> >
> > :)
>
> Mod_jk will use APR - that's certain. The only question is when and how
> to do the transition without affecting the stability of the code. Having
> an APR1.0 out is one of the requirements - I don't think we can release
> mod_jk, even from j-t-c, with dependencies on un-released library.
>
> There are already 2 proposals for how to do that - one with preserving the
> current common as a temporary solution, until we make sure it works with
> IIS/NES, and the other with removing the common utils and hoping things
> will work with IIS/NES.
>
> Right now the APR/common is not the main itch - it'll become pretty soon,
> at least for me ( I need mmap for the new connector )
I'm actually right now working on the thread locks for Windows, and then I
am going to start agitating for an APR release. We should have APR 1.0 out
the door soon-ish. I am hoping to have it released sometime in the next month
or two. :-)
Ryan
______________________________________________________________
Ryan Bloom rbb@apache.org
Covalent Technologies rbb@covalent.net
--------------------------------------------------------------
Re: [VOTE] Removal of mod_jk for Apache 2.0 from jakarta-tomcat f
or Tomcat 3.3
Posted by cm...@yahoo.com.
On Mon, 10 Sep 2001, Pier Fumagalli wrote:
> >> This is the third time we agree on something in less than 24 hours. This
> >> implies that either I'm getting old, or just plain silly...
> >
> > Now, if you could agree on merging mod_webapp and mod_jk, that would be
> > something...
>
> Slowwwwwww down... :) If mod_jk wants to start using APR, I believe we're
> talking, otherwise, I'm done with cross-platform porting, I live it to Ryan
> :)
Mod_jk will use APR - that's certain. The only question is when and how
to do the transition without affecting the stability of the code. Having
an APR1.0 out is one of the requirements - I don't think we can release
mod_jk, even from j-t-c, with dependencies on un-released library.
There are already 2 proposals for how to do that - one with preserving the
current common as a temporary solution, until we make sure it works with
IIS/NES, and the other with removing the common utils and hoping things
will work with IIS/NES.
Right now the APR/common is not the main itch - it'll become pretty soon,
at least for me ( I need mmap for the new connector )
Costin
Re: [VOTE] Removal of mod_jk for Apache 2.0 from jakarta-tomcat f
or Tomcat 3.3
Posted by Pier Fumagalli <pi...@betaversion.org>.
"cmanolache@yahoo.com" <cm...@yahoo.com> wrote:
> On Mon, 10 Sep 2001, Pier Fumagalli wrote:
>
>> "GOMEZ Henri" <hg...@slib.fr> wrote:
>>
>>> Ryan to became more than just a contributer :))))
>>
>> This is the third time we agree on something in less than 24 hours. This
>> implies that either I'm getting old, or just plain silly...
>
> Now, if you could agree on merging mod_webapp and mod_jk, that would be
> something...
Slowwwwwww down... :) If mod_jk wants to start using APR, I believe we're
talking, otherwise, I'm done with cross-platform porting, I live it to Ryan
:)
Pier