ASF subversion and git services commented on PROTON-865:

Commit 2b6240b113b68b213cb9d5b0711ed0da11c511e8 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=2b6240b ]

PROTON-865: Generate container and link IDs, move link creation to session

Allow user to set container id, generate a random UUID-style ID by default.

Default link names to per-container prefix+counter so user can ignore link 
names entirely,
set them all by hand, or mix user and generated names without risk of clash (by 
a safe prefix)

Moved create_sender and create_receiver methods from container to connection 
and session.

All other primary methods to create senders/receivers are now on session, with 
on connection to create on the default_session()

Dropped unused private_impl_ref.

The container still provides a shortcut to connect & create sender/receiver 
from URL.

> 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