Bill Barker wrote:
- Original Message -
From: "Costin Manolache" <[EMAIL PROTECTED]>
To:
Sent: Wednesday, January 12, 2005 4:14 AM
Subject: Re: Deprecation and JK2
A lot of the code is actually specific to the now-dead Jk2 - if the
native jk2 is gone, probably you shou
- Original Message -
From: "Costin Manolache" <[EMAIL PROTECTED]>
To:
Sent: Wednesday, January 12, 2005 4:14 AM
Subject: Re: Deprecation and JK2
>A lot of the code is actually specific to the now-dead Jk2 - if the
>native jk2 is gone, probably you should clea
A lot of the code is actually specific to the now-dead Jk2 - if the
native jk2 is gone, probably you should clean up this side as well.
- org.apache.jk.apr - the not-quite apr jni layer that connects to the
native objects, as well as 'in-process' launcher ( I doubt it can be
used by jk1.x ), al
Henri Gomez wrote:
+0
JK / JK2 are also very specific to our current AJP implemtation.
Maybe they should be called AJP instead ?
I thouhgt I had done enough damage with my package renaming and class
moving ;)
The renaming here is nearly all located in strings which are supposed to
be displayed
+0
JK / JK2 are also very specific to our current AJP implemtation.
Maybe they should be called AJP instead ?
PS: Happy New Year to all TC-DEV members :)
On Tue, 11 Jan 2005 10:44:17 +0100, Remy Maucherat <[EMAIL PROTECTED]> wrote:
> (Note: I'm talking about the Java code here)
>
> That code
(Note: I'm talking about the Java code here)
That code is IMO a bit messy. It's fast (it does its job and seems to
beat HTTP for proxying) and works, but I think a cleanup won't hurt.
Some of the issues:
- Deprecation (ex: JkMain is deprecated, supposedly to be replaced, but
I don't see anything
