[
https://issues.apache.org/jira/browse/QPID-7255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15289172#comment-15289172
]
ASF subversion and git services commented on QPID-7255:
-------------------------------------------------------
Commit 1744427 from [~lorenz.quack] in branch 'java/branches/6.0.x'
[ https://svn.apache.org/r1744427 ]
QPID-7255: [Java Broker, Java Client] Add support for message delivery delay
merged from trunk with:
$ svn merge -c 1743982,1744250 ^/qpid/java/trunk
manually resolved conflict in AbstractQueue and AbstractQueueTestBase
> 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
> Fix For: qpid-java-6.0.3, qpid-java-6.1
>
> 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]
