grpc
Node-based proxy
Some things I am interested in doing:
- Running the proxy in a Node.JS process
- Allowing arbitrary transport to the proxy (websocket, any other two-way link like WebRTC)
@wenbozhu supports literally anything. You give it a function for send(message) {} and it expects that message to end up at handleMessage(message) on the server. Also, the thing passed to send() is a ProtoBuf message so it supports binary serialization.
Thanks for the update!
Are you interested in implementing the grpc-web spec in the Node proxy?
https://github.com/grpc/grpc/blob/master/doc/PROTOCOL-WEB.md
There is already a Go proxy from Improbable. We are happy to review the Node proxy implementation and include the Node proxy in grpc-web interoperability test suite.
I've taken a stab at this, because we needed it ourselves for something: https://github.com/dataform-co/dataform/tree/master/tools/grpc-web-proxy
It seems to be working well for unary calls, I haven't had a chance to test it for streaming yet! Would be happy to discuss moving this somewhere official, but not sure I have the time to do that myself.
@lewish This looks promising! Let us check this out and we can discuss where it's more appropriate to host this later. Thanks!
@lewish I'm late for the party, your link goes to 404. Did you ever end up finishing that implementation so that it supports streaming as well? :-)
@lewish I'm late for the party, your link goes to 404. Did you ever end up finishing that implementation so that it supports streaming as well? :-)
maybe this? https://github.com/dataform-co/dataform/tree/master/grpc-web-proxy
@tiero Thank you! Unfortunately it says in the readme on that link that This has only been tested with unary gRPC calls. :-(
@petermetz I tested for my use case where I use grpc-web-text (ie. messages are encoded as base64) and is not supported either, guess is same reason only works for unary calls.