Feng,
> Am 11.03.2015 um 02:08 schrieb Feng Xiao <xiao...@google.com>:
>
> In case you are not yet aware of: Google has open-sourced its own RPC framework, named gRPC, about two weeks ago.
>
> gRPC website: http://www.grpc.io/
>
> It's basically Google's official RPC implementation for Protocol Buffers (in particular for proto3), but released as a separate project. For those of you who are interested in proto3, gRPC should be of interest to you as well :)
great to see the "coming out" of the RPC part of protobuf!
- it seems gPRC is 'the full stack' resting on HTTP2 & TCP, or is the transport intended to be replaceable/pluggable?
- does HTTP2 replace Websockets (which would have been my choice, but I'm not up to speed on the transport du jour)
- is there any relation to RPCZ (https://github.com/thesamet/rpcz)?
thanks!
Michael
ps: I'd be interested in hearing if anybody planning to plug this into a zeroMQ/protobuf stack
psps: we've been using a "raw" zeroMQ/protobuf stack without protoPC due to licensing restrictions on RPCZ (Apache license incompatible with GPL2)
On Tuesday, March 10, 2015 at 6:08:39 PM UTC-7, Feng Xiao wrote:In case you are not yet aware of: Google has open-sourced its own RPC framework, named gRPC, about two weeks ago.gRPC website: http://www.grpc.io/It's basically Google's official RPC implementation for Protocol Buffers (in particular for proto3), but released as a separate project. For those of you who are interested in proto3, gRPC should be of interest to you as well :)Excellent! However, can you please update and fix the broken link(s) to gRPC on the developer documentation page? Thanks!
In the section:"If you you want to try our new open-source RPC implementation gRPC (currently also in alpha release) – we recommend using proto3 for all new gRPC servers and clients as it avoids compatibility issues."The link to gRPC points to https://github.com/google/grpc-common, which is invalid. You probably meant https://github.com/grpc/grpc-common. Or perhaps you should be linking to the new grpc.io domain instead...--Kristian Erik Hermansen
--