[OASIS Issue Tracker] Commented: (AMQP-6) The received delivery-state does not make it clear what the implications of unset fields are

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ http://tools.oasis-open.org/issues/browse/AMQP-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=28861#action_28861 ] 

Angus Telfer commented on AMQP-6:
---------------------------------

Option (2) for sure!

> The received delivery-state does not make it clear what the implications of unset fields are
> --------------------------------------------------------------------------------------------
>
>                 Key: AMQP-6
>                 URL: http://tools.oasis-open.org/issues/browse/AMQP-6
>             Project: OASIS Advanced Message Queuing Protocol (AMQP) TC
>          Issue Type: Improvement
>         Environment: N/A
>            Reporter: Raphael Cohen
>            Assignee: Rob Godfrey
>            Priority: Minor
>
> The received delivery-state does not make it clear what the implications of unset fields are
> Received.section-number does not make it explicit what the implication of an unset field is;
> Received.section-offset does not make it explicit what the implication of an unset field is;
> The Received delivery-state is not an useful construct to send when either of these fields is unset as present. The current wording implying that the terminus does not consider the delivery partially transferred if either one or both of these fields is unset. See proposal for some possible resolutions.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira