[
https://issues.apache.org/jira/browse/CRYPTO-63?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15356542#comment-15356542
]
Dapeng Sun edited comment on CRYPTO-63 at 6/30/16 5:28 AM:
-----------------------------------------------------------
Thank Sebb for your comments,
{quote}
Note that JNA covers far more OSes than the JNI code, so it may be the only way
to make OpenSSL available on many platforms.
Unless there are serious problems with it, I think it would be better to
include the code, but include a warning in the documentation / release notes
that it may not be as reliable or performant as the JNI code. Users won't get
the JNA version unless they ask for it. For some platforms it may be the best
choice.
{quote}
I'm agree that JNA is an important feature, but I think move to next release
should be also reasonable. If JNA feature is strong demanded, we can speed up
the progress of the JNA release.
was (Author: dapengsun):
Thank Sebb,
{quote}
Note that JNA covers far more OSes than the JNI code, so it may be the only way
to make OpenSSL available on many platforms.
Unless there are serious problems with it, I think it would be better to
include the code, but include a warning in the documentation / release notes
that it may not be as reliable or performant as the JNI code. Users won't get
the JNA version unless they ask for it. For some platforms it may be the best
choice.
{quote}
I'm agree that JNA is an important feature, but I think move to next release
should be also reasonable. If JNA feature is strong demanded, we can speed up
the progress of the JNA release.
> Add JNA binding
> ---------------
>
> Key: CRYPTO-63
> URL: https://issues.apache.org/jira/browse/CRYPTO-63
> Project: Commons Crypto
> Issue Type: Improvement
> Reporter: Hendrik Saly
> Assignee: Hendrik Saly
>
> Needs benchmarking before merge.
> PR https://github.com/apache/commons-crypto/pull/47
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
