[
https://issues.apache.org/activemq/browse/AMQNET-137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=55182#action_55182
]
Timothy Bish commented on AMQNET-137:
-------------------------------------
Mark
I've reviewed the discussion on the ClientAcknowledge redelivery and I don't
really think we put something like this directly into NMS. The only logic for
redelivery in NMS.ActiveMQ that happens on the client side is for Transacted
sessions. Putting something like this Client Ack redelivery in something that
seems better suited for a higher level. This seems more like something that
would belong in a Camel.NET project than it does here as it sounds as if it
could apply to all the NMS providers.
> Add support for redelivery policy
> ---------------------------------
>
> Key: AMQNET-137
> URL: https://issues.apache.org/activemq/browse/AMQNET-137
> Project: ActiveMQ .Net
> Issue Type: New Feature
> Components: ActiveMQ
> Affects Versions: 1.1.0
> Reporter: Mark Keenan
> Assignee: Timothy Bish
> Priority: Minor
> Fix For: 1.2.0
>
> Attachments: RedeliveryPolicy.cs, RedeliveryPolicyTest.cs
>
>
> It would be nice if we could set redelivery policy (similar to the Java
> client). See this ActiveMQ mailing list thread for details:
> http://www.nabble.com/configuring-redelivery-with-NMS-td21714808.html#a21717670
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
