[ 
https://issues.apache.org/jira/browse/PROTON-1237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15366454#comment-15366454
 ] 

ASF subversion and git services commented on PROTON-1237:
---------------------------------------------------------

Commit 301ce7e575d14e5e4251fab02308150e430a472e in qpid-proton's branch 
refs/heads/master from [~aconway]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=301ce7e ]

PROTON-1237: go: let go build handle dependencies for go examples

Manual cmake dependencies were missing changes to the C library or headers and
causing crashes in out-of-date example executables.

Just run `go build` and `go test` every time, they get it right and don't
take any time if there is nothing to do.


> 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)
> To validate the work, add a single-threaded C example using the libuv library 
> for IO, and a multi-threaded C++ proton::container implementation also built 
> on libuv. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to