[
https://issues.apache.org/jira/browse/PROTON-1091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Ross updated PROTON-1091:
--------------------------------
Assignee: Kim van der Riet
> [Python binding] AMQP null type not sent on wire according to AMQP
> specification
> --------------------------------------------------------------------------------
>
> Key: PROTON-1091
> URL: https://issues.apache.org/jira/browse/PROTON-1091
> Project: Qpid Proton
> Issue Type: Bug
> Components: python-binding
> Reporter: Kim van der Riet
> Assignee: Kim van der Riet
> Fix For: 0.12.0
>
>
> When sending AMQP type null as the content of a message, the Python binding
> sends the message with no body at all, and similarly interprets a no-body
> AMQP type message as a null type. This violates the AMQP 1.0 specification on
> two counts:
> * A body MUST be present and be one of three types (section 3.2);
> * When sending an AMQP null type, there is an assigned AMQP type code (0x40)
> which should be used.
> This causes interoperability issues with other clients. For example, the C++
> client can't send a null type to a python client without a failure (or _visa
> versa_).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
