[
https://issues.apache.org/jira/browse/PROTON-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16201338#comment-16201338
]
ASF subversion and git services commented on PROTON-1618:
---------------------------------------------------------
Commit d0b641b75eb235d9959bab2792c0264522396321 in qpid-proton's branch
refs/heads/master from [~aconway]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=d0b641b ]
PROTON-1618: c proactor: unambiguous listen success/fail indicator
Changed the use of events in all 3 proactor implementations as follows:
After a call to pn_proactor_listen():
- on success, dispatch PN_LISTENER_OPEN before any PN_PROACTOR_ACCEPT
- on failure, set the pn_listener_condition() and dispatch PN_LISTENER_CLOSE
An application can tell from the first event received (OPEN vs. CLOSE) if the OS
listen call succeeded or failed.
> Give unambiguous indication when server listen operation succeeds or fails
> --------------------------------------------------------------------------
>
> Key: PROTON-1618
> URL: https://issues.apache.org/jira/browse/PROTON-1618
> Project: Qpid Proton
> Issue Type: Improvement
> Components: proton-c
> Reporter: Justin Ross
> Assignee: Alan Conway
> Labels: api
> Fix For: proton-c-0.18.0
>
>
> The C proactor API provides events to indicate when an async listen operation
> has succeeded or failed, but the semantics are a little unclear. The C++ API
> lacks the required events.
> Simplify & clarify the C API, and add the missing events in C++.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
