[ https://issues.apache.org/jira/browse/PROTON-865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14571362#comment-14571362 ]
ASF subversion and git services commented on PROTON-865: -------------------------------------------------------- Commit 8074793b84a6402b01f3639e8cf8fed6b5ba54cc 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=8074793 ] PROTON-865: Example and cmake cleanup, minor code cleanup. - Optionally enable C++ in top level cmake for examplesb. Still works without a C++ compiler. - Move cpp examples to the /examples dir, renamed for consistent exe naming conventions. - Integrate example build & auto-test with cmake - Improved exception handling - Simplified exception handling. - Removed nascent logging code, logging should be handled centrally in C library. > 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)