[
https://issues.apache.org/jira/browse/PROTON-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15120374#comment-15120374
]
ASF subversion and git services commented on PROTON-1095:
---------------------------------------------------------
Commit 9c03b28b0e3865aa892f0fa79650bd6c25759a22 in qpid-proton's branch
refs/heads/master from [~aconway]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=9c03b28 ]
PROTON-1095: c++: connection_engine error handling, get rid of exceptions.
Engine no longer throws any exceptions itself, all connections and transport
errors are reported to the handler which can choose to throw or not.
This is consistent with error handling for the Container.
Added condition::empty()
Removed process_nothrow
Removed disconnect
Return pair<size_t, bool> from io_read rather than throwing on stream close.
> Error handling
> --------------
>
> Key: PROTON-1095
> URL: https://issues.apache.org/jira/browse/PROTON-1095
> Project: Qpid Proton
> Issue Type: Improvement
> Components: cpp-binding
> Reporter: Andrew Stitcher
> Assignee: Andrew Stitcher
> Fix For: 0.12.0, 0.13.0
>
>
> The C++ binding needs a disciplined and effective way to handle protocol (and
> transport) errors.
> Currently the API has some error events, however if they are not handled the
> program will just hang - it would be better in this case to throw an
> exception so that the program doesn't just hang.
> Another issue is creating error states (attaching a condition) when closing a
> connection/session/link - there should be some straightforward way to
> indicate the error to your peer.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
