News for hackers. Stuff that matters.
Re:GRPC: A high performance, open source, general RPC framework by wbsun on Friday February 27, 2015 @12:31AM (#9117335)
What are the benefits of using HTTP rather than TCP directly? I guess one of them is easy to pass firewalls. Anything else makes HTTP better than raw TCP for RPC?
Re:GRPC: A high performance, open source, general RPC framework by ejona86 on Friday February 27, 2015 @09:55AM (#9119120)
HTTP/2 is quite featureful and provides most of the advanced needs that gRPC has; HTTP/2 is pretty similar to what we would make ourselves if gRPC used TCP directly.

Using HTTP/2 though also allows fitting into the wider web ecosystem of proxies, reverse proxies, load balancers/TLS terminators, and developer familiarity.

Re:GRPC: A high performance, open source, general RPC framework by teraflop on Friday February 27, 2015 @01:14AM (#9117467)
There wouldn't be much benefit to using HTTP/1.1, but HTTP/2 makes it easy to pipeline and multiplex requests over a single TCP connection.
Re:GRPC: A high performance, open source, general RPC framework by somethingnew on Friday February 27, 2015 @12:54AM (#9117403)
Not having to worry about calculating the length of the message before transferring it?
Re:GRPC: A high performance, open source, general RPC framework by ejona86 on Friday February 27, 2015 @09:47AM (#9119064)
gRPC actually still has to calculate the length of a message before transferring it.