[
https://issues.apache.org/jira/browse/QPID-5285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16715027#comment-16715027
]
Robbie Gemmell commented on QPID-5285:
--------------------------------------
If I'm understanding the snippet above it is adding an annotation of
"CreationTime"? The spec requires peers which don't understand an annotation to
react by detaching the link with a not0implemented error, except when prefixed
"x-opt-" in which case they must ignore it, so I'd wonder if it should have
that prefix added given no negotiation of support is being performed.
Ignoring that, "CreationTime" feels a bit off since its actually describing the
arrival time at the broker rather than the creation time of the message, which
was earlier (and if so desired that point can already be stamped in the
immutable properties.creation-time field of the message by the senders).
> [AMQP 1.0] timestamped messages not supported
> ---------------------------------------------
>
> Key: QPID-5285
> URL: https://issues.apache.org/jira/browse/QPID-5285
> Project: Qpid
> Issue Type: Bug
> Components: C++ Broker
> Affects Versions: 0.24
> Reporter: Gordon Sim
> Assignee: Gordon Sim
> Priority: Major
> Fix For: Future
>
> Attachments: Incoming.cpp
>
>
> There is a timestamping feature in qpidd that if enabled sets the timestamp
> field of the AMQP 0-10 delivery-properties when a message arrives at the
> broker.
> There is no equivalent field defined in the AMQP 1.0 specification. Thus this
> feature is at present not supported over 1.0 (i.e. messages delivered over
> 1.0 will not have the timestamp set).
> An annotation could be defined to convey the timestamp for 1.0 messages. This
> could also be used in translating between 0-10 and 1.0 formats.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
