[
https://issues.apache.org/jira/browse/PROTON-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16201339#comment-16201339
]
ASF subversion and git services commented on PROTON-1618:
---------------------------------------------------------
Commit 31d5ba096aa850e49b0f2475a3c1ef9f171f9a3c in qpid-proton's branch
refs/heads/master from [~aconway]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=31d5ba0 ]
PROTON-1618: c++ container: unambiguous listen success/fail indicator
Added listener_handler::on_open() to indicate a successful listen.
After a call to container::listen():
- on success, call listener_handler::on_open() before any call to
listener_handler::on_accept()
- on failure, call listener_handler::on_error() followed by
listener_handler::on_close()
An application can tell from the first event received (on_open() vs.
on_close()) if the
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
