|
|
| Author |
Message |
|
| 0x6e6562 |
 Posted: Sun Sep 02, 2007 5:10 pm |
 |
|
|
User
Joined: 12 Jul 2007
Posts: 250
|
Hi all,
I've been using Hessian encoding within my message payloads and there
is also the use of JSON to achieve the same goal. I was just wondering
if the AMQP type encoding is a viable candidate to encode the
application layer data, as this makes no assumptions about the
marshalling capabilities of other peers, or the encoding not suited
for this layer? Has anybody discussed or made any practical
experiences with this aspect?
Thanks,
Ben
_______________________________________________
rabbitmq-discuss mailing list
rabbitmq-discuss@lists.rabbitmq.com
http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
Post recived from mailinglist |
|
|
| Back to top |
 
|
| Guest |
| Posted: Mon Sep 03, 2007 1:59 pm |
|
|
|
Guest
|
Ben Hood wrote:
> I've been using Hessian encoding within my message payloads and there
> is also the use of JSON to achieve the same goal. I was just wondering
> if the AMQP type encoding is a viable candidate to encode the
> application layer data, as this makes no assumptions about the
> marshalling capabilities of other peers, or the encoding not suited
> for this layer? Has anybody discussed or made any practical
> experiences with this aspect?
The AMQP type encoding has not been designed as a general purpose data
encoding. So Hessian, JSON, or similar would be a better choice, IMHO.
Matthias.
_______________________________________________
rabbitmq-discuss mailing list
rabbitmq-discuss@lists.rabbitmq.com
http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
Post recived from mailinglist |
|
|
| Back to top |
|
| 0x6e6562 |
| Posted: Wed Sep 05, 2007 8:39 pm |
|
|
|
User
Joined: 12 Jul 2007
Posts: 250
|
Matthias,
> The AMQP type encoding has not been designed as a general purpose data
> encoding. So Hessian, JSON, or similar would be a better choice, IMHO.
Thanks for the confirmation on this as this was my view as well from a
usability perspective. The consequence of this is that different peers
have to agree a priori on the higher level data encoding, which I
guess is not the end of the world either.
Ben
_______________________________________________
rabbitmq-discuss mailing list
rabbitmq-discuss@lists.rabbitmq.com
http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
Post recived from mailinglist |
|
|
| Back to top |
|
| tonyg |
| Posted: Thu Sep 06, 2007 9:20 am |
|
|
|
User
Joined: 07 Nov 2006
Posts: 199
|
Ben Hood wrote:
> The consequence of this is that different peers
> have to agree a priori on the higher level data encoding, which I
> guess is not the end of the world either.
That's true, although the BasicProperties contentType and
contentEncoding fields are intended to carry MIME content-type (e.g.
"application/json", "application/x-hessian" (in the absence of an
official IETF Hessian registration)) and MIME content-encoding
identifiers respectively, which can help out here.
Regards,
Tony
--
[][][] Tony Garnock-Jones | Mob: +44 (0)7905 974 211
[][] LShift Ltd | Tel: +44 (0)20 7729 7060
[] [] http://www.lshift.net/ | Email: tonyg@lshift.net
_______________________________________________
rabbitmq-discuss mailing list
rabbitmq-discuss@lists.rabbitmq.com
http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
Post recived from mailinglist |
|
|
| Back to top |
|
| 0x6e6562 |
| Posted: Fri Sep 07, 2007 8:00 pm |
|
|
|
User
Joined: 12 Jul 2007
Posts: 250
|
> That's true, although the BasicProperties contentType and
> contentEncoding fields are intended to carry MIME content-type (e.g.
> "application/json", "application/x-hessian" (in the absence of an
> official IETF Hessian registration)) and MIME content-encoding
> identifiers respectively, which can help out here.
That's a fair point, I hadn't thought of that.
Thx, Ben
_______________________________________________
rabbitmq-discuss mailing list
rabbitmq-discuss@lists.rabbitmq.com
http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
Post recived from mailinglist |
|
|
| Back to top |
|
|
|
All times are GMT
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You cannot download files in this forum
|
|
|
Digg It
Del.icio.us
Reddit
Facebook
Stumble Upon
Technorati
