[rabbitmq-discuss] How to define a timeout on jsonRpcClient calls

[mysurf mail]

Hi All,
Still regarding the JsonRpc
1. I would also love to control the  json rpc channel properties -   mainly
autodelete.
You see, the queues of JSONRpcClient are not deleted when the client go of.
and since they clients queue name is randomly given, the queues are packed
each restart.

2. in the example = client server constructor
HelloJSonClient - jsonrpc client gets Hello in the routing key
HelloJsonServer - jsonrpc server gets Hello in the queuename

Why should the routing key in the client be assigned? where is the
connection between the two?
Shouldn't it be autogenereated like the queue name in the client side?
thanks.

On Tue, Mar 29, 2011 at 3:48 PM, Emile Joubert <emile at rabbitmq.com> wrote:

> Hi,
>
>
> On 29/03/11 14:14, mysurf mail wrote:
>
>  I saw the place you pointed for me to change (line 174). As I
>> understand,  you suggest I would change it and recompile the rabbitmq
>> source ? That is possible but it would be a pain every time I will want
>> to upgrade a client version.
>>
>
> I agree - it is not convenient to maintain your own set of patches. We are
> planning on introducing this feature in the core library though.
>
>
>  so I have two questions
>> 1. I know that you are being asked that question a lot - but can I get a
>> patch?
>>
>
> We prefer to distribute code via the rabbit source repositories, rather
> than patches.
>
>
>  2. If I will go down in the root of changing the source -  you mentioned
>> it is an experience. Do you know if someone else did it and if it works
>> fine?
>>
>
> A bug has been filed to implement your suggestion. The implementation will
> appear on the branch named "bug23515". Unfortunately it is not possible to
> predict when this might be complete, but keep an eye on future release
> notes.
>
>
> Regards
>
> Emile
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20110330/95bea417/attachment.htm>