[rabbitmq-discuss] Using rabbitmq-http2 (was: simple.publish over the JSON RPC interface)

Tue Aug 11 19:22:15 BST 2009

On Tue, Aug 11, 2009 at 4:19 AM, Tony Garnock-Jones<tonyg at lshift.net> wrote:
> The AMQP channel
> object is set to deliberately not answer poll() requests until
> sessionTimeout/2 has elapsed -- giving long-polling behaviour -- so in
> the case of the poll() method, you want the x-json-rpc-timeout header to
> let the operation take *at least* as long as sessionTimeout/2.
>
> I did it that way because it's nice and simple, has fairly predictable
> behaviour, and generally seemed like a reasonable first approach. Is
> there a better way of doing it?

It seems to me that there's no one-size-fits-all timeout for poll.
Some apps will want non-blocking polling and others will want it to
block indefinitely until there's work to do.  Wouldn't it be better to
just have an explicit timeout parameter to poll()?

Cheers,
-n8

-- 
http://n8gray.org