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

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

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

Lorenz Quack commented on AMQP-130:
-----------------------------------

Furthermore, I am not sure why this field is mandatory on the first Transfer.
My understanding is that AMQP in general tries to be as efficient as possible and there is a reasonable default (zero) for the message format.

I think the spec in an evolution of the spec it should allow omitting the message format and assume zero (0) as the default.

For what it is worth this is already the behaviour of the Qpid broker-j.

> 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)