[
https://issues.apache.org/jira/browse/PROTON-1304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15494231#comment-15494231
]
ASF GitHub Bot commented on PROTON-1304:
----------------------------------------
GitHub user astitcher opened a pull request:
https://github.com/apache/qpid-proton/pull/80
PROTON-1304: Changed OpenSSL interface code to not need time at all
This PR is specially for @kgiusti to review
- Used the openssl session client cache without having own cache that needs
expiring.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/astitcher/qpid-proton openssl-session-cache
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/qpid-proton/pull/80.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #80
----
----
> SSL code shouldn't need to know the time (shouldn't use the platform
> dependent parts of proton-c)
> -------------------------------------------------------------------------------------------------
>
> Key: PROTON-1304
> URL: https://issues.apache.org/jira/browse/PROTON-1304
> Project: Qpid Proton
> Issue Type: Improvement
> Reporter: Andrew Stitcher
> Assignee: Andrew Stitcher
>
> Currently the interface to OpenSSL keeps it's own cache of sessions separate
> from the cache held in OpenSSL itself.
> It needs to be able to purge this cache when the entries expire, so it needs
> to know the time to figure out how old the cache entries are.
> If we eliminate this cache and just use the underlying OpenSSL cache then we
> wouldn't need to know the time and this code would be platform independent
> (or at least as platform independent as OpenSSL code itself).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
