[
https://issues.apache.org/jira/browse/QPID-7255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rob Godfrey updated QPID-7255:
------------------------------
Attachment: QPID-7255.diff
I've attached a patch which supports the notion of checking for a "not valid
before" header in the message.
Before proceeding down this path, would be good to get others to review the
approach. Before committing I think we'd want to promote the "not valid
before" to a synthetic attribute of the AMQMessageHeader so that (for instance)
in AMQP 1.0 we could model this as a MessageAnnotation rather than a message
header... moreover the message implementations could cache the value once it
has been parsed.
There also should be a client side change to allow specifying the delivery
delay in the address string for producers.
> Support delivery delay
> ----------------------
>
> Key: QPID-7255
> URL: https://issues.apache.org/jira/browse/QPID-7255
> Project: Qpid
> Issue Type: New Feature
> Components: Java Broker
> Reporter: Keith Wall
> Attachments: QPID-7255.diff
>
>
> Some enterprise messaging systems provide a delayed delivery feature whereby
> a publisher can provide a delivery time when sending the message, with the
> Broker taking care of not making the message available to consumers until
> that time is reached. The Java Broker should provide the same feature.
> In the Java space, JMS 2.0 has standardised this feature, however there is
> no reason why the feature could not be made available to older JMS 1.1
> clients using a Qpid specific header. Also if the BURL or ADDR address
> could hint to the Producer that delivery delay was required for all messages
> produced by it, this would mean message delay could be turned on from
> configuration alone.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
