Right now a project I'm working with is using protobuf to pass data chunks back and forth between client and server. What may be the better conceptual design in this case is to actually expose an API through gRPC. gRPC seems to support Node.js, but does it support google's own closure-library extension to javascript?--
---
You received this message because you are subscribed to the Google Groups "Closure Library Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to closure-library-d...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
go/grpc-webRe: grpc being part of closure, goog.net.streams was developed for grpc-web; and goog.net.rpc (to be added) will have a generic stub for streaming and non-streaming requests + cors optimization ... but the node style grpc clients etc need stay outside closure (for the sake of both grpc and closure).
On Wed, May 18, 2016 at 8:28 AM, 'Wenbo Zhu' via Closure Library Discuss <closure-lib...@googlegroups.com> wrote:go/grpc-webRe: grpc being part of closure, goog.net.streams was developed for grpc-web; and goog.net.rpc (to be added) will have a generic stub for streaming and non-streaming requests + cors optimization ... but the node style grpc clients etc need stay outside closure (for the sake of both grpc and closure).What does 'go/grpc-web' mean? Are we to understand that there's a browser-based grpc client that it hasn't been released to the public yet?
Are their plans to release it to the public and, if so, is there a time table?
-- David Sankel