Am 2020-12-11 um 17:41 schrieb Rémy Maucherat:
On Fri, Dec 11, 2020 at 5:36 PM Mark Thomas <ma...@apache.org> wrote:

On 11/12/2020 16:24, Michael Osipov wrote:
Am 2020-12-10 um 15:07 schrieb ma...@apache.org:
+ * @deprecated  The scope of the APR/Native Library will be reduced
in Tomcat
+ *              10.1.x / Tomcat Native 2.x onwards to only include
those
+ *              components required to provide OpenSSL integration
with the NIO
+ *              and NIO2 connectors.

I think there should *not* be a Tomcat Native 2.x for the following
reasons:

* It has been mentioned numerous times that Tomcat Native is a bad name
without a good meaning
* > 50 % of the essential parts of Tomcat Native will be gone. It won't
be Tomcat Native anymore as previously.
* Since the APR connector is deprecated, de facto, it does not logically
make sense to evolve Tomcat Native to a new major version. Just
counter-intuitive.

My counter proposal is to split Tomcat Native, phase it out and
introduce Tomcat OpenSSL (Bridge) (libtcopenssl.so) or similar. The name
should clearly say what it does.

Using a new name is already one of the options. That possibility was
mentioned in one of these threads about a week ago.

You won't going to continue the APRLifecycleListener, will you?

There will almost certainly need to be something like it. I had imagined
it would get a new name but hadn't given much though to what that name
should be.

WDYT?

We need to be careful when we use other organisation's trademarks in our
product names. Some like:

Apache Tomcat Bridge to OpenSSL

would be fine. The other option is to give it an entirely new name.

Apache Tomcat Phoenix

for example. (I haven't done any checks on that name. It may be
completely unsuitable - it is just an example).


I'm not sure this native code will stay for that long (replaced with
integrated Java code possibly), so I'm not convinced a name is needed. ->
modules/openssl ?

Are you referring to Panama? Or any substantial improvement to SunJSSE?

I don't expect both happen before Java 17/18 and since none of them will be available for 8/11 JNI and the OpenSSL wrapper will likely live for another at least 5 or 8 years.



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Reply via email to