grpc from JavaScript in the browser

[John Langley]

Any updates on the availability / road-map for browser support of grpc?

TIA

-- Langley 

[Eric Anderson]

On Tue, Mar 10, 2015 at 2:00 PM, John Langley <dig...@gmail.com> 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. 

[Louis Ryan]

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.

[kil...@gmail.com]

From this comment, I conclude that gRPC can be used in a browser for RPC calls - except for streaming.

Haven't yet found an example...

[Eric Anderson]

I think the comment was saying possible in the theoretical sense. Not possible with code available today.

--
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 grpc-io+unsubscribe@googlegroups.com.
To post to this group, send email to grp...@googlegroups.com.
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.

[Paul Grosu]

I prefer the practical sense :)  By empowering users through the addition of documentation for the shared C library and how to properly create a surface API by integrating with it, for sure that will ease your pain of having to create the JavaScript surface API for them. 

It's just a little effort and it will save you so much time down the road.

~p

On Monday, August 1, 2016 at 11:50:43 AM UTC-4, Eric Anderson wrote:

I think the comment was saying possible in the theoretical sense. Not possible with code available today.

On Mon, Aug 1, 2016 at 7:07 AM, <kil...@gmail.com> wrote:

From this comment, 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 <dig...@gmail.com> 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 grpc-io+u...@googlegroups.com.

To post to this group, send email to grp...@googlegroups.com.

[travis...@gmail.com]

https://github.com/tmc/grpc-websocket-proxy might be of interest

[Cameron Stuart]

grpc from javascript in browsers would be such a breakthrough.

Sadly, I have to hold off until such a day. I can't afford to make my API's work with and without.

But grpc and especially protocol buffers aspect make a very exciting proposition. What protobuf things I have tested so far shows such a dramatic improvement on efficiency.

I guess for the moment, I'll move to protobuf response data out of regular endpoints and then to grpc when (if?) it is available.

[Jeff Willette]

Have you seen this? https://github.com/improbable-eng/grpc-web