>From this comment <http://stackoverflow.com/questions/35065875/how-to-bring-a-grpc-defined-api-to-the-web-browser#comment58727032_35166533>, I conclude that gRPC can be used in a browser for RPC calls - except for streaming. Haven't yet found an example...
On Thursday, March 12, 2015 at 9:16:11 PM UTC+2, Louis Ryan wrote: > > Its probably a bit more accurate to say that while some browsers do have > trailers support the API to interact with HTTP is weaker than we would like > and we haven't done the testing necessary to thrash out what is and is not > possible. There is hope however > > https://fetch.spec.whatwg.org/ > > but its hard to say when something like this would land. > > On Wednesday, March 11, 2015 at 3:36:10 PM UTC-7, Eric Anderson wrote: >> >> On Tue, Mar 10, 2015 at 2:00 PM, John Langley <[email protected]> wrote: >> >>> Any updates on the availability / road-map for browser support of grpc? >>> >> >> No work is currently being done for browser support of gRPC. gRPC >> requires HTTP Trailers, which is not available in browsers, which is a bit >> of a show-stopper. >> >> We do recognize that having browser support would make gRPC universal. We >> haven't given up on the browser, but are inclined to believe it may need a >> bit different technology. >> >> Having an issue where we could discuss potential solutions wouldn't be a >> bad idea, if you wanted to make one. >> > -- You received this message because you are subscribed to the Google Groups "grpc.io" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/b56a547a-db3f-46f7-ab38-dd0a98c9dae9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
