Hey Marek,<div><br></div><div>We're currently evaluating looking at this in production for use in delivering large amounts of messages in single transactions from lots of web applications where a persistent connection can't be maintained with RabbitMQ and the large volume of connect/disconnects are problematic.</div>
<div><br></div><div>Currently my thinking was this was the best way to go but I am concerned that it will be deprecated. Will this be maintained for the foreseeable future?</div><div><br></div><div>Regards,</div><div><br>
</div><div>Gavin<br><br><div class="gmail_quote">On Mon, Feb 7, 2011 at 8:04 AM, Marek Majkowski <span dir="ltr"><<a href="mailto:majek04@gmail.com">majek04@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On Sun, Feb 6, 2011 at 16:14, James Carr <<a href="mailto:james.r.carr@gmail.com">james.r.carr@gmail.com</a>> wrote:<br>
> Aside from digging through the sample provided for the JSON-RPC<br>
> channel is there any kind of documentation floating around that<br>
> describes the services and procedures supported?<br>
<br>
</div>No, I'm afraid the only option is reading the source code.<br>
<br>
<br>
We have few in-house initiatives on how to replace<br>
jsonrpc with something more supported, but the topic<br>
is complex and requires a lot of engineering.<br>
<br>
Cheers,<br>
<font color="#888888"> �Marek<br>
</font><div><div></div><div class="h5">_______________________________________________<br>
rabbitmq-discuss mailing list<br>
<a href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a><br>
<a href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a><br>
</div></div></blockquote></div><br></div>