You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Alan Conway (JIRA)" <ji...@apache.org> on 2016/07/15 15:42:20 UTC

[jira] [Resolved] (PROTON-1237) C connection_engine interface and libuv example driver.

     [ https://issues.apache.org/jira/browse/PROTON-1237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alan Conway resolved PROTON-1237.
---------------------------------
    Resolution: Fixed

The C engine is completed with a simple libuv client example. 
Completing a multi-threaded libuv container has been separated to PROTON-1259

> 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: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org