2 ms·
I guess it only makes sense if you are already using protobuf everywhere else in your stack. Specially if you are leveraging GRPC[0] which is already profobuf o
by vruiz 11y ago
I guess it only makes sense if you are already using protobuf everywhere else in your stack. Specially if you are leveraging GRPC[0] which is already profobuf over HTTP. The network tab problem could be solved by an extension, or browsers could offer the tools built-in if there were to become a trend.
[0] http://www.grpc.io/ http://www.grpc.io/
- soldergenie 11y agoGrpc doesn't work over the browser. This is stated explicitly in the FAQ. See https://groups.google.com/forum/#!topic/grpc-io/5Ic8MKgltwY https://groups.google.com/forum/#!topic/grpc-io/5Ic8MKgltwY
- rektide 11y agoIt's rather painful that they don't seem to have any design docs up for their HTTP transport, leaving it to things like FAQ entries to explain these details. This was my first thought too- grpc does this.
- soldergenie 11y agoThe protocol is documented - https://github.com/grpc/grpc-common/blob/master/PROTOCOL-HTTP2.md https://github.com/grpc/grpc-common/blob/master/PROTOCOL-HTT... However, you still need the FAQ to figure out that browser transport isn't supported