[rabbitmq-discuss] JSON-RPC reference?
james.r.carr at gmail.com
Mon Feb 7 15:18:14 GMT 2011
I would love to create a websocket based API for rabbitmq (using STOMP
or whatever) but my current lack of erlang skills prevent me from
I'm working my way through Erlang and OTP in Action, so I pray that
the skills I need will come quickly. I always tout websockets allowing
browsers to communicate directly with message brokers as being the
future in presentations I give. :)
On Mon, Feb 7, 2011 at 9:05 AM, Brian Jones <bkjones at gmail.com> wrote:
> On Mon, Feb 7, 2011 at 8:04 AM, Marek Majkowski <majek04 at gmail.com> wrote:
>> On Sun, Feb 6, 2011 at 16:14, James Carr <james.r.carr at gmail.com> wrote:
>> > Aside from digging through the sample provided for the JSON-RPC
>> > channel is there any kind of documentation floating around that
>> > describes the services and procedures supported?
>> No, I'm afraid the only option is reading the source code.
>> We have few in-house initiatives on how to replace
>> jsonrpc with something more supported, but the topic
>> is complex and requires a lot of engineering.
> Are you suggesting that jsonrpc is one or more of:
> 1. Not well supported
> 2. Deprecated
> If it's going to be replaced at some point, I can understand the complete
> lack of any docs outside of source code, but then what will be replacing it?
> Should I hold off sifting source code until that gets released? Are docs
> being neglected because you want to discourage adoption until some other
> facility is made public?
> If it's not going to be replaced at some point in the nearer term, is it
> unreasonable to request a doc for it that is similar to the one for the
> Management API?
>> rabbitmq-discuss mailing list
>> rabbitmq-discuss at lists.rabbitmq.com
> Brian K. Jones
> My Blog http://www.protocolostomy.com
> Follow me http://twitter.com/bkjones
More information about the rabbitmq-discuss