[
https://issues.apache.org/jira/browse/QPID-4627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13701924#comment-13701924
]
Gordon Sim commented on QPID-4627:
----------------------------------
Re: creation_time property, as mentioned on the dev list I think this is the
wrong solution. For 1.0 the creation-time should be used (its a matter of two
lines or so to record it during parsing). On 0-10 I would use the timestamp as
set on the delivery-properties of the received message (not the timestamp as
set by the broker). That way over AMQP 1.0 the solution isboth compliant with
the selector filter as specified and with JMS. On 0-10 behaviour will still be
compliant with JMS without doing anything worse than is already being done as
regards the 0-10 spec.
> Implement remaining special identifiers
> ---------------------------------------
>
> Key: QPID-4627
> URL: https://issues.apache.org/jira/browse/QPID-4627
> Project: Qpid
> Issue Type: Sub-task
> Reporter: Andrew Stitcher
> Assignee: Andrew Stitcher
>
> The remaining JMS specified identifiers are:
> amqp.correlation_id
> amqp.message_id
> amqp.creation_time
> amqp.jms_type
> The ones remaining from the AMQP Apache filters spec are:
> amqp.to
> amqp.reply_to
> amqp.absolute_expiration_time
> - amqp.durable (it's not clear this is really there as distinct from
> amqp.delivery_mode)
> - amqp.delivery_count (it's not clear this is really there as distinct from
> amqp.redelivered)
> In order to implement these special identifiers there will need to be extra
> work to abstract some of these values from the 0-10 or 1-0 message code.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
