tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bill Barker" <>
Subject Re: Deprecation and JK2
Date Wed, 12 Jan 2005 02:44:57 GMT

----- Original Message -----
From: "Costin Manolache" <>
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 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 ), also common.JniHandler
>- ChannelJni, ChannelShm, ChannelUn, Shm - specific to jk2.

I think that proxy_ajp is hoping to be able to use ChannelUn someday.  It's
no more Jk2 specific than ChannelSocket is.

>Maybe it would be a good idea to rename the remaining files ( but please
>not org.apache.ajp - it would be confusing since this is the name of the
>very old connector package ).
>What is the story with in-process ? Is it still supported with jk1.x ?

Only the (very) old 3.3 JniHandler at the moment.


Remy Maucherat wrote:
> 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 to the user when there's an error, and also in comments ->
> low impact stuff.
>> PS: Happy New Year to all TC-DEV members :)
> Rémy

To unsubscribe, e-mail:
For additional commands, e-mail:

This message is intended only for the use of the person(s) listed above as the intended recipient(s),
and may contain information that is PRIVILEGED and CONFIDENTIAL.  If you are not an intended
recipient, you may not read, copy, or distribute this message or any attachment. If you received
this communication in error, please notify us immediately by e-mail and then delete all copies
of this message and any attachments.

In addition you should be aware that ordinary (unencrypted) e-mail sent through the Internet
is not secure. Do not send confidential or sensitive information, such as social security
numbers, account numbers, personal identification numbers and passwords, to us via ordinary
(unencrypted) e-mail.

View raw message