[rabbitmq-discuss] Problems getting reply_to to work

[Robert Buck]

Hi, Thanks.

Doing a recursive grep, I see several references in the amqp ruby project
where this exists. In my case, since I am doing request-reply, here is one
notable example:

./examples/patterns/request_reply/client.rb
./examples/patterns/request_reply/server.rb

Immediate is also referenced in the RabbitMQ docs,

http://www.rabbitmq.com/api-guide.html

Cheers,

Bob

On Sun, Sep 30, 2012 at 9:13 AM, Matthias Radestock
<matthias at rabbitmq.com>wrote:

> Robert,
>
>
> On 30/09/12 13:56, Robert Buck wrote:
>
>> Yes, "immediate" was cribbed from the sample code, as was much of the
>> code I put together, well, at least the concepts were cribbed that is.
>>
>
> Could you post a link to the sample code, please, so that Michael can
> remove the use of 'immediate' from it?
>
>
>  So I should yank immediate?
>>
>
> Yes, but that has nothing to do with the problem you were seeing.
>
>
>  I am not sure why 'response_queue.subscribe' doesn't trigger the setting
>> of the name. It's rather weird in that regard, neither the client nor
>> the server see the generated queue name. I would be guessing that the
>> Ruby amqp gem is broken in this regard?
>>
>
> 'broken' might be a bit harsh, 'surprising' perhaps ;) Anyway, this is one
> for Michael.
>
> Regards,
>
> Matthias.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20120930/f3dab7c6/attachment.htm>