OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

amqp message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [OASIS Issue Tracker] (AMQP-130) Clarify Transfer message-format field description


    [ https://issues.oasis-open.org/browse/AMQP-130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=67344#comment-67344 ] 

Rob Godfrey commented on AMQP-130:
----------------------------------

Robbie's interpretation of the meanings (and the rationale) is correct.  Setting a "default" would change the semantics - then multi-transfer message of a message of format 1 would require every transfer explicitly set the format to 1, since if omitted the default (0) would be implied, and that would fall foul of the "every transfer in the same delivery must use the same format" rule.

The rule could perhaps be more clearly expressed as "The first transfer of any delivery MUST set the mesage-format.  Where a delivery consists of more than one transfer, the subsequent transfers MAY omit the message-format.  If the message-format is set the it MUST take the same value as that on the first transfer for the delivery."

> Clarify Transfer message-format field description
> -------------------------------------------------
>
>                 Key: AMQP-130
>                 URL: https://issues.oasis-open.org/browse/AMQP-130
>             Project: OASIS Advanced Message Queuing Protocol (AMQP) TC
>          Issue Type: Improvement
>          Components: Transport
>            Reporter: Lorenz Quack
>              Labels: Clarification
>
> The AMQP specification states in section 2.7.5 [1] about the message-format field of the Transfer performative:
> This field MUST be specified for the first transfer of a multi-transfer message and can only be omitted for continuation transfers. It is an error if the message-format on a continuation transfer differs from the message-format on the first transfer of a delivery.
> There are two things I would like the specification to be more explicit about:
> * Whether the field is required on single transfer deliveries (see also AMQP-128).
> * How to handle the error condition. Do we reject the message? Detach the Link? End the Session? Close the Connection? What ErrorCondition should be used?
> [1] http://docs.oasis-open.org/amqp/core/v1.0/os/amqp-core-transport-v1.0-os.html#type-transfer



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]