qpid-proton mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PROTON-865) C++ reactor client binding
Date Tue, 01 Sep 2015 17:35:46 GMT

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

ASF subversion and git services commented on PROTON-865:
--------------------------------------------------------

Commit 182fc591812a9a9bf1d233b43b74cc4dfa19e47d in qpid-proton's branch refs/heads/cjansen-cpp-client
from [~aconway]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=182fc59 ]

PROTON-865: Minor fixes and clean-up.

Separate counted_ptr.hpp from facade.hpp
Rename PN_UNIQUE_OR_AUTO_PTR as PN_UNIQUE_PTR
Fix bugs in CMake boost compile flags.
Fix bugs in shared pointer conversions and unit test.
Make counted private.


> C++ reactor client binding
> --------------------------
>
>                 Key: PROTON-865
>                 URL: https://issues.apache.org/jira/browse/PROTON-865
>             Project: Qpid Proton
>          Issue Type: New Feature
>         Environment: C++
>            Reporter: Cliff Jansen
>            Assignee: Cliff Jansen
>
> This JIRA tracks initial work on a C++ binding to the Proton reactor event based model
with an eye to providing an API very similar to the python client.  As stated on the Proton
list, the broad goals are:
>   to make it easy to write simple programs
>   natural to build out more complicated ones
>   very similar API to the Python client
>   lean and performant
> The initial introduction with accompanying HelloWorld can be found at
>   https://github.com/apache/qpid-proton/pull/18
> Ongoing work is proceeding in my github account in branch cpp-work
>   https://github.com/cliffjansen/qpid-proton/tree/cpp-work
> commit 1453f57ca3f446450ef654505548f1947cb7a0f1 adds listener support, exceptions and
a logging interface.
> The initial implementation will provide no thread safety guarantees, but the bone structure
should allow that to be added later with no API change.  I still hold out hope of eventually
allowing multiple threads processing separate connections concurrently.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message