[
https://issues.apache.org/jira/browse/PROTON-1949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16638452#comment-16638452
]
Robbie Gemmell commented on PROTON-1949:
----------------------------------------
I don't think your desire really works. Messages with no header do still have a
priority, 4. The spec is clear that its semantically the same whether the
header is sent or not, or the value is populated or not. I don't think you can
reasonably treat the field/value's presence or not as definitely indicating it
'had one assigned' when that value is 4. For example, to complicate matters, I
think perhaps in the past proton-c actually sent the value 4 if you included a
header but hadn't explicitly set the priority to 4.
(The JMS client also omits a header when it can, as its a waste of bytes and
work done encoding/decoding it)
> no message header if priority == default
> ----------------------------------------
>
> Key: PROTON-1949
> URL: https://issues.apache.org/jira/browse/PROTON-1949
> Project: Qpid Proton
> Issue Type: Bug
> Reporter: michael goulish
> Priority: Major
>
> Proton does not send a message header if there would be nothing in it but the
> priority field, and if the priority was set to the default value (4).
> At the router level, we are allowing the user to set priorities on addresses.
> Those priorities will be given to any message sent to that address if the
> message otherwise had no priority set.
> So - we need to be able to distinguish between messages that were assigned
> the default priority, and messages in which the priority was left undefined.
> We would like proton to send the priority field in the message header if the
> user sets any priority. Then we will be able to interpret no header, or no
> priority field in the header as "no priority was assigned".
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
