[ 
https://issues.apache.org/jira/browse/QPID-7255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15283996#comment-15283996
 ] 

Rob Godfrey edited comment on QPID-7255 at 5/15/16 10:42 PM:
-------------------------------------------------------------

Committed an updated version of the previously attached patch.

On the client side the delivery delay can be provided in the address (e.g. 
{noformat}ADDR: queue ; { link: { delay: 10000 } }{noformat} or 
{noformat}BURL:direct:////queue?deliveryDelay='10000'{noformat}).

Potentially the client might want to detect whether the broker it is working 
with supports delivery delay.

I've held off adding a system test which would be by its definition vulnerable 
to timing issues on slower/busy machines.  Documentation also still needs to be 
added.


was (Author: rgodfrey):
Committed an updated version of the previously attached patch.

On the client side the delivery delay can be provided in the address (e.g. 
"ADDR: queue ; { link: { delay: 10000 } }" or 
"BURL:direct:////queue?deliveryDelay='10000'").

Potentially the client might want to detect whether the broker it is working 
with supports delivery delay.

I've held off adding a system test which would be by its definition vulnerable 
to timing issues on slower/busy machines.  Documentation also still needs to be 
added.

> 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]

Reply via email to