[
https://issues.apache.org/jira/browse/PROTON-1505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16339561#comment-16339561
]
Andrew Stitcher commented on PROTON-1505:
-----------------------------------------
I don't think that addressing point 2 of the issues is part of the design of
proton:
Proton is essentially about messaging semantics (albeit low level messaging
semantics) rather than frame level details. From a semantic point of view there
is no difference between the priority header field being absent and the
priority value being 4. So I see no reason to expose the absence of the field.
> Message header defaults only work if no header present
> ------------------------------------------------------
>
> Key: PROTON-1505
> URL: https://issues.apache.org/jira/browse/PROTON-1505
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-c
> Reporter: Kim van der Riet
> Assignee: Andrew Stitcher
> Priority: Major
> Labels: codec
> Fix For: proton-c-0.21.0
>
>
> An error in the qpid-interop-tests JMS headers test showed that where there
> is no message priority on the wire, the C++ and Python client APIs do not
> return the default value as mandated by the AMQP spec. In particular, the
> priority is returned with a value of 0 rather than the default value of 4.
> This raises two issues:
> 1. Setting the default value (in particularly for priority, where a priority
> system may be adopted that is not default, and the missing value may need to
> have a value other than 4).
> 2. (C++) Gaining access to the transport headers so that there is an ability
> to distinguish between the default and the value being actually present on
> the wire.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
