[
https://issues.apache.org/jira/browse/PROTON-1512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16175006#comment-16175006
]
Robbie Gemmell commented on PROTON-1512:
----------------------------------------
On the comments around whether its ok for the router to drop an aborted message
not yet partly passed on toa peer, would I be right to assume thats around
message-routing and that for link-routing the transfers would always be
forwarded as-is?
On Alans A/B scenario, to complicate matters slightly more I'd note that A may
already be subject to potential hang/stall/never finish even without aborted
transfers, if session flow control is in play enforcing protons 'session
capacity' and the window becomes full before the message is complete. I believe
that only effectively happens if you set a max frame size currently though.
> Expose the "aborted" flag for transferred deliveries
> ----------------------------------------------------
>
> Key: PROTON-1512
> URL: https://issues.apache.org/jira/browse/PROTON-1512
> Project: Qpid Proton
> Issue Type: New Feature
> Components: proton-c
> Reporter: Ted Ross
> Assignee: Alan Conway
> Labels: api
> Fix For: proton-c-0.18.0
>
>
> As we develop support for message streaming in Qpid Dispatch Router (i.e.
> frames for large multi-frame messages are forwarded to destinations as they
> arrive, before the complete message is received), there is a need to handle
> the case where a received message is never completed.
> The AMQP protocol has a provision for this in the "aborted" flag in the
> transfer performative. If the router is in the process of streaming a large
> message from sender to receiver and the sender drops before completing the
> delivery, the router can send a transfer to the downstream receivers with the
> "aborted" flag set. This would indicate that the message should not be
> processed and would not cause any framing errors on the link.
> Proton does not currently expose this capability in its API (There is a
> pn_link_abort in the C header file, but it is commented out and not
> implemented).
> In order to properly handle the failure cases for message streaming, this
> feature must be usable in Proton.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
