[ https://issues.apache.org/jira/browse/PROTON-2108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16937153#comment-16937153 ]
Gordon Sim commented on PROTON-2108: ------------------------------------ The spec states: {quote} if the default-outcome is not set, and no outcomes are provided, then the accepted outcome MUST be supported by the source {quote} That is not the same as saying that *only* the accepted outcome is supported. I would argue the issue as described is an enhancement (of mostly theoretical interest), not a bug (neither outcomes nor default outcome are mandatory). The critical priority also seems unjustified to me. Or is there a concrete use case that requires this feature? (In practice I think wider use of this feature of the spec would generally be detrimental to interoperability.) > 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: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org