[rabbitmq-discuss] RPC response/reply for RabbitMQ - Timeouts

[Chris]

If you do figure out how to use client timeouts, you may also want to
consider using per-message TTL if you don't care about the message anymore
after a timeout.  This can save unnecessary processing of messages that no
longer have an interested participant.  On the other hand, if you want the
message processed, even after the client times out, then you better not do
this.

https://www.rabbitmq.com/ttl.html#per-message-ttl

-Chris


On Tue, Jun 11, 2013 at 11:41 AM, Tim Watson <tim at rabbitmq.com> wrote:

> On 11 Jun 2013, at 01:53, JayD wrote:
>
> All information is old that I have seen on this.  Is there yet a way to
> define a client side timeout on an rpc style call.  I find it hard to
> believe that one would have to leave the request hanging if the server is
> not up and running.
>
> Does anyone have a good solution for this at this point in time?  On the
> client side I am using pika.
>
>
> This kind of problem is generally solved using threads, or some kind of
> non-blocking I/O event loop. I have no idea how Pika does it - I think it
> depends on which kind of consumer you've set up - but I'd suggest you try
> asking on the pika mailing list -
> https://groups.google.com/forum/#!forum/pika-python.
>
> Cheers,
> Tim
>
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20130611/5c01f8ff/attachment.htm>