[rabbitmq-discuss] Management console argument syntax (was Re: Failed to add an exchange via the web interface)

Mon Mar 26 14:14:18 BST 2012

I think letting the mgmt user select a JSON type is likely to be much 
friendlier than selecting an AMQP type. And yes, apps and plugins should 
be encouraged to use interoperable types.

Having said that, I find the pseudo-Excel syntax rather confusing. I am 
more inclined to just put a select box there.

Cheers, Simon

On 26/03/12 13:42, Tony Garnock-Jones wrote:
> On 26 March 2012 06:33, Simon MacMullen <simon at rabbitmq.com
> <mailto:simon at rabbitmq.com>> wrote:
>
>     I was really determined to avoid having a type select in the UI. But
>     I'm not sure that can be avoided. I'll file a bug.
>
>
>  From the "Works for Excel" file: how about a magic escape into some
> kind of JSONish syntax?
>
> That is, if the user types
>
> 12345
>
> they get the longstr "12345";
>
> Hello
>
> they get the longstr "Hello";
>
> =12345
>
> they get a numeric type with value 12345;
>
> ="Hello"
>
> they get the longstr "Hello";
>
> =Hello
>
> they get a syntax error (it isn't JSON).
>
> JSON's numbers, strings, booleans, arrays and maps ought to be enough
> for the majority of cases. (It might be worth an Application Note on the
> website regarding the mapping from AMQP table data to and from JSON, and
> encouraging applications and plugins to stick to the common
> interoperable subset...)
>
> Tony
> --
> Tony Garnock-Jones
> tonygarnockjones at gmail.com <mailto:tonygarnockjones at gmail.com>
> http://homepages.kcbbs.gen.nz/tonyg/

-- 
Simon MacMullen
RabbitMQ, VMware