[
https://issues.apache.org/jira/browse/PROTON-1062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15120242#comment-15120242
]
ASF subversion and git services commented on PROTON-1062:
---------------------------------------------------------
Commit 7b4fa65a20da04ce32bd570b6552f7287adee665 in qpid-proton's branch
refs/heads/master from [~aconway]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=7b4fa65 ]
PROTON-1062: c++: Improved example test runner for connection_engine tests.
Fixes a test hang on windows.
Monitor stdout to for 'ready' messages instead of testing ports: faster, more
portable.
Detect & raise broker errors, restart broker for remaining tests.
Keep all process output for verificiation and error reporting.
Clean up stray processes.
> proton::engine as a client example
> ----------------------------------
>
> Key: PROTON-1062
> URL: https://issues.apache.org/jira/browse/PROTON-1062
> Project: Qpid Proton
> Issue Type: Improvement
> Components: cpp-binding
> Affects Versions: 0.12.0
> Reporter: Scott Matloff
> Assignee: Alan Conway
> Priority: Minor
>
> The existing example which demonstrates the proton::engine functionality is a
> broker. To better demonstrate the disassociation between the connection and
> the container, I think there should be an example using memory streams.
> The example would look like:
> 1) Create some data
> 2) Encode the data using the engine
> 3) Place the result into a memory buffer
> 4) Decode the data from the buffer using a different engine instance
> 5) Display the data
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
