[rabbitmq-discuss] ACK modes in the STOMP adapter

[Aman Gupta]

Is there a way to handle flow control? I would like rabbitmq to stop sending
me new messages until I am done processing old ones, so that new messages
don't get lost.
  Aman

On Tue, Jul 1, 2008 at 3:41 AM, Tony Garnock-Jones <tonyg at lshift.net> wrote:

> Hi Aman,
>
> It does support "ack: client", but acknowledgements are not used to perform
> flow control: instead, they can be used to arrange for at-least-once
> deliveries.
>
> Essentially, "ack: client" is translated into setting "noack" to "false" on
> the "basic.consume" AMQP method that results from a STOMP "SUBSCRIBE"
> operation. Please see the AMQP specification for the semantics of the
> "noack" flag.
>
> Regards,
>  Tony
>
>
> Aman Gupta wrote:
>
>> It seems the STOMP adapter does not support ack modes (
>> http://stomp.codehaus.org/Ack+Modes). If I subscribe to a queue using
>> ack: client, I continue to get additional messages from the queue, even
>> before I respond with an ACK for the original message.
>>
>>  Aman Gupta
>>
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> rabbitmq-discuss mailing list
>> rabbitmq-discuss at lists.rabbitmq.com
>> http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>>
>
>
> --
>  [][][] Tony Garnock-Jones     | Mob: +44 (0)7905 974 211
>   [][] LShift Ltd             | Tel: +44 (0)20 7729 7060
>  []  [] http://www.lshift.net/ | Email: tonyg at lshift.net
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20080701/c1d6fe05/attachment.htm