[
https://issues.apache.org/jira/browse/PROTON-2108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17046475#comment-17046475
]
Robert Godfrey commented on PROTON-2108:
----------------------------------------
To start with something I think we can all agree on
bq. However I doubt anyone will be helped by clarification in a spec erratum at
this point.
+1 :-)
As a bit of background here, I think the thought processes (such as they were,
and digging up from my cloudy memory) were that there wasn't any sort of
agreement about which outcomes implementations would actually be capable of
supporting amongst reject/release/modify, and so the lowest common denominator
was chosen - everything always has to support accepted, and that the ability to
support more than that needs to be advertised.
> supported source outcomes not set
> ---------------------------------
>
> Key: PROTON-2108
> URL: https://issues.apache.org/jira/browse/PROTON-2108
> Project: Qpid Proton
> Issue Type: Bug
> Affects Versions: proton-c-0.29.0
> Reporter: Robbie Gemmell
> Priority: Critical
>
> From looking at some recent traces, it appears that the bindings (at least
> for python, but probably others) do no set the outcomes (or default-outcome)
> field on its source terminus, although they do use/support all the outcomes.
> To a peer that actually inspects the outcomes to influence behaviour this
> strictly means only Accepted is supported, which can lead to issues (e.g it
> might accept a message then drop it, rather than release/modify/reject it,
> under cases it couldn't be processed).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
