qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jiri Daněk (JIRA) <j...@apache.org>
Subject [jira] [Commented] (PROTON-1618) Give unambiguous indication when server listen operation succeeds or fails
Date Thu, 12 Oct 2017 11:13:00 GMT

    [ https://issues.apache.org/jira/browse/PROTON-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16201797#comment-16201797

Jiri Daněk commented on PROTON-1618:

Looking at apache TravisCI https://travis-ci.org/apache/qpid-proton/builds, after the last
commit the clang build fails. I've been rerunning the clang build in my travis, and it keeps
failing https://travis-ci.org/apache/qpid-proton/builds/286822832. The GCC build maybe takes
somewhat longer time to finish than before, but I haven't tried it enough times, maybe just
Travis became slow.

> 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

To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org

View raw message