Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>SO user "default locale" should get the honor for this, but he/she has only answered via a comment. So just to make it very clear what my choice was I'll answer my own question.</p> <p>I've decided to go with Google Protocol Buffers, which in my opinion has much better support for moving objects back and forth between Java and .Net than JSON. Because I have a lot of experience with C#, and a lot of existing C#-defined classes, I've selected Marc Gravell's protobuf-net program for the .Net end, and Google's own support for the Android end (no - see edit). This implies that I'm defining the objects in C#, not in .proto files - protobuf-net generates the .proto files from which I then generate the Java code.</p> <p>Incidentally, as the transport mechanism I'm using a little-known program called naga on the Android end. <a href="http://code.google.com/p/naga/" rel="nofollow">http://code.google.com/p/naga/</a> Naga seems to work fine, and is well-documented and has sample programs, and should be better known in my opinion.</p> <p>EDIT:</p> <p>OK, I've got it working now to my satisfaction. Here's what I'm using:</p> <p>Google Protocol buffers as the interchange format: <a href="https://developers.google.com/protocol-buffers/" rel="nofollow">https://developers.google.com/protocol-buffers/</a></p> <p>Marc Gravell's protobuf-net at the C# end: <a href="http://code.google.com/p/protobuf-net/" rel="nofollow">http://code.google.com/p/protobuf-net/</a></p> <p>A program called called protostuff at the Java end: <a href="http://code.google.com/p/protostuff/" rel="nofollow">http://code.google.com/p/protostuff/</a></p> <p>(I prefer protostuff to the official Google Java implementation of protocol buffers due to Google's implementation being based on the Java objects being immutable.)</p> <p>Actually, I'm not using pure protocol buffers as the interchange format - I prefix the data with the name of the (outermost) class being transmitted. This makes the data self-identifying for deserializing at the other end.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload