You are viewing a plain text version of this content. The canonical link for it is here.
Posted to proton@qpid.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2014/11/20 17:15:35 UTC
[jira] [Commented] (PROTON-750) Have distinct API to indicate SSL
layer is not really implemented
[ https://issues.apache.org/jira/browse/PROTON-750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14219543#comment-14219543 ]
ASF subversion and git services commented on PROTON-750:
--------------------------------------------------------
Commit b4e06d34a83cd942ea88a5e19ad938be312ed2ae in qpid-proton's branch refs/heads/master from [~astitcher]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=b4e06d3 ]
PROTON-749, PROTON-750: Merge these changes into development stream.
> Have distinct API to indicate SSL layer is not really implemented
> -----------------------------------------------------------------
>
> Key: PROTON-750
> URL: https://issues.apache.org/jira/browse/PROTON-750
> Project: Qpid Proton
> Issue Type: Improvement
> Components: proton-c
> Affects Versions: 0.9
> Reporter: Andrew Stitcher
> Assignee: Andrew Stitcher
> Labels: API
>
> Currently the pn_ssl_domain() API is overloaded to indicate that SSL support isn't really present (it return NULL) in this case.
> However this has proven to be brittle in the case the SSL support is partially there. For example in the continuing implementation of SSL for Windows.
> It make more sense to unambiguously say that SSL if fully present with a specific API.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)