[
https://issues.apache.org/jira/browse/PROTON-1237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15380156#comment-15380156
]
ASF subversion and git services commented on PROTON-1237:
---------------------------------------------------------
Commit e9f9eef00e50f93c49f2eeec66bcfa9045e771d6 in qpid-proton's branch
refs/heads/master from [~aconway]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=e9f9eef ]
PROTON-1237: c: connection_engine event logging.
Environment variable PN_TRACE_EVENT=1 prints proton C event names using the
transport trace log facility. Mostly useful for low-level debugging while doing
binding work but might be of use to users in some cases.
> C connection_engine interface and libuv example driver.
> -------------------------------------------------------
>
> Key: PROTON-1237
> URL: https://issues.apache.org/jira/browse/PROTON-1237
> Project: Qpid Proton
> Issue Type: New Feature
> Components: proton-c
> Affects Versions: 0.12.2
> Reporter: Alan Conway
> Assignee: Alan Conway
> Fix For: 0.14.0
>
>
> The C++ and Ruby bindings have a connection_engine interface: it gathers
> together the functionality of pn_connection pn_transport and pn_collector to
> enable handler-style programming against a single connection, with no
> assumptions about IO or threading.
> Some of this can be back-ported to C to make it easier to do reactive
> programming in C without using the pn_reactor (which forces IO and threading
> choices on the user)
> Create a C version of the C++ io::connection_engine and use it as the
> implementation of the C++ and Go binding engines.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
