We currently use Apache Thrift for this, and have had success with it over the past year of use. Some others have mentioned using Protobufs on the mailing list. JSON is also an alternative. Thrift and Protobufs both require code generation, but have a more compact representation and faster serialization / deserialization because of it. JSON is human-readable and still quite compact compared to alternatives like XML serialization.<div>
<br></div><div>Michael</div><div><br><div class="gmail_quote">On Tue, Aug 18, 2009 at 8:57 AM, Jim Irrer <span dir="ltr"><<a href="mailto:irrer@umich.edu">irrer@umich.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi -<br><br>We are replacing much of our SOAP infrastructure with AMQP, and<br>one problem we are looking at is how to wrap an AMQP call so that<br>it has a nice programming interface. Basically we want to serialize<br>an object on one side and de-serialize on the other side, and do it<br>
in a language independent way (we use Java C#, and C++).<br><br>I am looking at REST (Representational State Transfer), XML-RPC,<br>and possibly JSON-RPC. Ideally we would like something that<br>automatically does the serialization/de-serialization or generates<br>
code that does it.<br><br>Has anyone found a technology that they like?<br><br>Thanks,<br><br>- Jim<br><font color="#888888"><br clear="all">Jim Irrer <a href="mailto:irrer@umich.edu" target="_blank">irrer@umich.edu</a> (734) 647-4409<br>
University of Michigan Hospital Radiation Oncology<br>
519 W. William St. Ann Arbor, MI 48103<br>
</font><br>_______________________________________________<br>
rabbitmq-discuss mailing list<br>
<a href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a><br>
<a href="http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a><br>
<br></blockquote></div><br></div>