User Tools

Site Tools


info:cross-language_communication

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
info:cross-language_communication [2016-06-15 15:35]
sam [Binary Formats]
info:cross-language_communication [2016-06-15 15:52] (current)
sam
Line 16: Line 16:
   * Protocol Buffers from Google   * Protocol Buffers from Google
     * Now has an RPC implementation,​ [[http://​www.grpc.io/​|gRPC]] ((initially heard about it from http://​eli.thegreenplace.net/​2016/​grpc-sample-in-c-and-python/​))     * Now has an RPC implementation,​ [[http://​www.grpc.io/​|gRPC]] ((initially heard about it from http://​eli.thegreenplace.net/​2016/​grpc-sample-in-c-and-python/​))
-      * Doesn'​t directly support browser, at least not yet; there is at least one REST proxy: https://​github.com/​gengo/​grpc-gateway ((see e.g. https://​coreos.com/​blog/​gRPC-protobufs-swagger.html)),​ which support ​Swagger ​UI+      * Doesn'​t directly support browser, at least not yet; there is at least one REST proxy: https://​github.com/​gengo/​grpc-gateway ((see e.g. https://​coreos.com/​blog/​gRPC-protobufs-swagger.html)),​ which supports ​Swagger
       * Both synchronous and asynchronous APIs       * Both synchronous and asynchronous APIs
       * RPC methods support streaming data in either direction (in Python, this is exposed to the server as an iterator parameter for streaming from client, and the server can "​yield"​ results to stream to the client)       * RPC methods support streaming data in either direction (in Python, this is exposed to the server as an iterator parameter for streaming from client, and the server can "​yield"​ results to stream to the client)
info/cross-language_communication.txt · Last modified: 2016-06-15 15:52 by sam