[
https://issues.apache.org/jira/browse/PROTON-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16201341#comment-16201341
]
ASF subversion and git services commented on PROTON-1618:
---------------------------------------------------------
Commit 485cdbd3f680772e081ca05fbda97c0f271c676e in qpid-proton's branch
refs/heads/master from [~aconway]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=485cdbd ]
PROTON-1618: c++ tests use test_port.h for listen ports
POSIX: Use bind(0) with SO_REUSEADDR and hold the socket to acquire a port that
can safely be used for listen()
Windows: Use bind(0) to pick a port, but close the socket immediately. In theory
another process could steal the port between bind() and listen(), but in
practice this seems to be very unlikely.
The previous randomize-and-retry approach makes it hard to test the sequence of
events for listen(), since the random retry may cause multiple listen errors
even when it is finally successful.
> 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
