|
|
|
|
|
|
by abra_kadabra
3190 days ago
|
|
|
First for a bit of background. How much data will you be pushing across? Things are easier if you can send full objects instead of partial objects. How much does latency matter? If this has to be as close to real time as possible (ie. stock prices etc), or can this be 1 second updates? Using Protocol Buffers works well if you need to be very optimized, JSON is really nice for being extremely widely supported but special care needs to be taken for having API versions if you make drastic changes to the API I think what would be nice would be to know a little bit more about your intended use case, I would say I typically like to build web apps more than native apps because then the server code and client code can be updated as a single unit, instead of having older native clients out in the wild and having to support then until the users decide to update, but some use cases it's better to have a native client. |
|
|