[rabbitmq-discuss] Regarding the non-blocking call of "amqp_simple_wait_frame"
david at rabbitmq.com
Mon Jan 17 17:01:17 GMT 2011
Tony Garnock-Jones <tonygarnockjones+rabbitmq at gmail.com> writes:
> 2011/1/17 Alexandre Kalendarev <akalend at mail.ru>
>> the rabbitmq-c client d't have no-blocking i/o.
> A cheap hack would be to use select() (etc) to wait for some input to become
> available, and then call amqp_simple_wait_frame.
While it might be possible to make that work in simple consumer cases,
it seems distinctly fragile to me. If librabbitmq breaks under such
use, you get to keep both parts!
Staff Engineer, RabbitMQ
SpringSource, a division of VMware
More information about the rabbitmq-discuss