[rabbitmq-discuss] channel.flow

[Aman Gupta]

Thanks! I'm trying to figure out what the behavior should be in the
async ruby library, since blocking is not possible. I probably need to
maintain a local queue per channel..

Is there something like Basic.PublishOk that I can hook up to a
callback on MQ::Queue#publish?

mq = MQ.new
mq.queue('name').publish('hi') do
  puts 'message was received!'
end

This way the user can atleast keep track of published messages to
ensure none are lost by the local process and channel queues.

  Aman

On Tue, Apr 14, 2009 at 11:51 PM, Matthias Radestock
<matthias at lshift.net> wrote:
> Amos,
>
> Amos Elliston wrote:
>> On Apr 14, 2009, at 1:09 AM, Matthias Radestock wrote:
>>> It shouldn't be hard to add support for channel.flow to your lib. I'd
>>> be happy to answer any questions on how it should work.
>>
>> i was going to add it to mine. do you know of a good way to test
>> channel.flow. can i force rabbit to send it?
>
> At the rabbit erlang prompt, evaluate
>   memsup:set_sysmem_high_watermark(0.01).
> to lower the memory threshold. You should see a message
>   alarm_handler: {set,{system_memory_high_watermark,[]}}
> appear in the rabbit.log.
>
> To raise the threshold again, evaluate
>   memsup:set_sysmem_high_watermark(0.95).
> at which point you should see
>   alarm_handler: {clear,system_memory_high_watermark}
> in the logs.
>
>
> Matthias.
>
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>