[rabbitmq-discuss] how to send a message including a array via .net client?

Wed Jan 5 09:01:42 GMT 2011

where did you find that spec?  I wonder what map, list, and values look
like. I remember one compact message format rendered XML as value
pairs seperated by 0x00. If not now, perhaps RabbitMQ will support these
message formats in the future.  If you took a tunneling approach, binary is
a pretty good catch all.

1. render to Json (or other format), 2. render to binary.

I suppose the downside is it's less transparent at the tansport level.
-Steven
On 4 January 2011 11:25, Chen Houwu <chenhouwu at gmail.com> wrote:

> Thanks for all the above answers.
>
> I studied the AMQP 0.9.1 and AMQP 1.0 specification, and found:
>
> in 0.9.1:  only  opaque binary message content (here means the
> *playload*) is supported.
>
> but in 1.0 :  message content can be one of the following data type
> A. opaque binary data: note, in particular, that the section is not an
> instance of the AMQP binary type).
> B. amqp-data: zero or more encoded AMQP values)
> C. amqp-map: zero length or consist of a single encoded instance of an
> AMQP map.
> D. amqp-list: zero length or consist of a single encoded instance of
> an AMQP list.
>
> RabbitMQ's .net Client is supporting up to AMQP 0.9.1, so message
> content does not support those data types other than opaque binary.
>
> AMQP 1.0 has contained it's one message content format similar to JSON
> and Protocol Buffer.
>  _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20110105/38e6ecfb/attachment.htm>