Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Thu, 19 Nov 2015 15:08:11 +0000 (UTC)
From: "Aleksey Yeschenko (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12914491.1447944818000.123371.1447945691025@Atlassian.JIRA>
In-Reply-To: <JIRA.12914491.1447944818000@Atlassian.JIRA>
References: <JIRA.12914491.1447944818000@Atlassian.JIRA>
 <JIRA.12914491.1447944818462@arcas>
Subject: [jira] [Updated] (CASSANDRA-10735) Support netty openssl
 (netty-tcnative) for client encryption
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CASSANDRA-10735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Aleksey Yeschenko updated CASSANDRA-10735:
------------------------------------------
    Fix Version/s: 3.x

> Support netty openssl (netty-tcnative) for client encryption
> ------------------------------------------------------------
>
>                 Key: CASSANDRA-10735
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10735
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Andy Tolbert
>             Fix For: 3.x
>
>
> The java-driver recently added support for using netty openssl via [netty-tcnative|http://netty.io/wiki/forked-tomcat-native.html] in [JAVA-841|https://datastax-oss.atlassian.net/browse/JAVA-841], this shows a very measured improvement (numbers incoming on that ticket).   It seems likely that this can offer improvement if implemented C* side as well.
> Since netty-tcnative has platform specific requirements, this should not be made the default, but rather be an option that one can use.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)