3 ms·
I like grpc but I wish it was easier to use from the browser. My favorite solution on github only has 5 stars. > failing to set attributes as protocols have ev
by grizzles 9y ago
I like grpc but I wish it was easier to use from the browser. My favorite solution on github only has 5 stars.
> failing to set attributes as protocols have evolved over time has been a genuine problem.
Can you explain what you mean? The evolution of datagrams seems like it's one of grpc's core strengths.
- Veratyr 9y agoHave you seen https://github.com/grpc-ecosystem/grpc-gateway https://github.com/grpc-ecosystem/grpc-gateway? It generates a reverse proxy that converts proto <-> JSON and will even output a Swagger definition you can use with a JS client library.
- grizzles 9y agoI didn't know about the swagger bit. That sounds cool; I'll check it out. This is the one I meant: https://github.com/gabrielgrant/grpc-bus-websocket-proxy-client https://github.com/gabrielgrant/grpc-bus-websocket-proxy-cli...
- weitzj 9y agoThere is grpc web in the works, but that will take some time. We use the swagger route and the grpcgateway. Check out the CoreOS blog post. Also a really great tool is https://github.com/moul/protoc-gen-gotemplate https://github.com/moul/protoc-gen-gotemplate We use this right now to generate an Elm JSON client for grpcgateway (without Swagger)