[
https://issues.apache.org/jira/browse/QPIDJMS-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16580054#comment-16580054
]
ASF subversion and git services commented on QPIDJMS-391:
---------------------------------------------------------
Commit 8f0e35bd5502c77227a5d3eb8f8c67b90bdd49c8 in qpid-jms's branch
refs/heads/master from [~gemmellr]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-jms.git;h=8f0e35b ]
QPIDJMS-391: reorg the dep props/entries for clarity, fix some typos
> Add support for the use of native OpenSSL based providers
> ---------------------------------------------------------
>
> Key: QPIDJMS-391
> URL: https://issues.apache.org/jira/browse/QPIDJMS-391
> Project: Qpid JMS
> Issue Type: New Feature
> Components: qpid-jms-client
> Reporter: Johan Stenberg
> Priority: Minor
> Labels: performance
> Fix For: 0.36.0
>
>
> It would be great to have an option to use netty-tcnative-boringssl-static
> instead of the java based SSL provider. In the ActiveMQ Artemis this was
> implemented as part of https://issues.apache.org/jira/browse/ARTEMIS-1649
> In Netty 4.1.26 a new OpenSslX509KeyManagerFactory for easier configuration
> was introduced. https://github.com/netty/netty/pull/8084
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]