ASF subversion and git services commented on PROTON-865:

Commit 9d5bf7d7706a247bf1badec8c2b09fc0d08c0421 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=9d5bf7d ]

PROTON-865: Separate API doc for C++ binding from C binding, minor cleanup in 
C++ binding.

# Conflicts:
#       examples/cpp/example_test.py
#       proton-c/bindings/cpp/include/proton/cstdint.hpp
#       proton-c/bindings/cpp/include/proton/encoder.hpp
#       proton-c/bindings/cpp/include/proton/link.hpp
#       proton-c/bindings/cpp/include/proton/messaging_handler.hpp
#       proton-c/bindings/cpp/include/proton/type_traits.hpp
#       proton-c/bindings/cpp/include/proton/types.hpp
#       proton-c/bindings/cpp/src/decoder.cpp
#       proton-c/bindings/cpp/src/interop_test.cpp
#       proton-c/bindings/cpp/src/messaging_handler.cpp
#       proton-c/docs/api/index.md

> 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

Reply via email to