[
https://issues.apache.org/jira/browse/PROTON-656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14119935#comment-14119935
]
Ken Giusti commented on PROTON-656:
-----------------------------------
For consideration: given the new event model, I'd like to see these errors
(also?) reported as events if possible.
For example, if a framing error is hit, the transport should issue a
TRANSPORT_ERROR event, and the app can then determine the error details by
examining the transport object.
Having error handling also handled by the application's event handling code
makes sense to me.
> pn_transport_close_{head, tail} no longer return an error code on framing
> error.
> --------------------------------------------------------------------------------
>
> Key: PROTON-656
> URL: https://issues.apache.org/jira/browse/PROTON-656
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-c
> Affects Versions: 0.8
> Reporter: Ken Giusti
> Priority: Blocker
> Fix For: 0.8
>
>
> In the 0.7 release, the transport interfaces pn_transport_close_head() and
> pn_transport_close_tail() used to return an error should the close occur at
> an 'unexpected' point on the protocol (framing error, for example).
> The behavior no longer occurs on trunk. This results in an API change.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
