Is support for "real" GRPC in browsers through Streams API still ongoing?

[Fabio Monte]

Hi again,

Following my question https://groups.google.com/g/grpc-io/c/RUG-nzLXSWY , and still reading the docs/forums/github etc, I dare ask in a more clear way :

 ---> Is support for "native" / "real" GRPC in browsers (and not an approximation of what we have currently with PROTOCOL-WEB.md / GRPC-Web + need to rely on a proxy for translation), which if we read the docs was at least in need of release of the Streams API (which has landed for quite some time particularly in Chrome-ish family) which was mandatory since browsers were lacking the primitives needed to implement fully GRPC.. is it STILL, then, an active path of development CURRENTLY followed by the community / Google ?

Are the chokepoints in particular places ?

Thanks for any clarification.

[Fabio Monte]

I dare BUMP this thread. Thanks for any insights from "insiders" kinda. Thanks

[Ivy Zhuang]

Thank you for asking. If this feature looks interesting but is not available yet is open source I would encourage you to open issues to do the feature request on github, adding your use cases and any suggestions.

Once available you would see from release notes and here as well.

[Piotr Morgwai Kotarbinski]

Hi,

This seems like a major (sub-) project, so, unless google already has been having a plan for this, it seems unlikely that google will dedicate resources to it just because few ppl starred a feature request on github ;-)

Hence, the information if google has such plans may be useful for ppl from the open-source community who would consider dedicating their time to develop this themselves (ie: if google has a plan for this already, then it probably does not make sense to duplicate the efforts).

Cheers!

[Fabio Monte]

Thanks for answers. INDEED as Morgwai mentioned, that would be great to know the "official" stance of Google about that, if it is doable with current APIs, etc ...perhaps if not yet doable what would be required still as primitives on the browsers APIs.

Thanks

[wen...@google.com]

There are two different questions:

1) will the grpc-web JS client use streams API? Yes, for response streams.  Request streams are not yet finalized on whatwg. We are doing some Chrome Origin Trial right now.  

2) will protocol translation be required even with streams? Yes, e.g. to support HTTP/1.1, or address Web platform constraints.  

Feel free to file a github issue on grpc/grpc-web on any doc issues or roadmap discussion.   Thanks.

[Fabio Monte]

Thank you very much for answer wen...(at)google.com. 

For your point 2, could you explain a little? 

-->  It would mean we would still need some kind of proxy then, is that correct ? If so I wonder, is really a "fully native" GRPC "in the browser" (no need for proxy etc..it would "just work") just a dream? Is there still some hope for example if one would abandon http1.1 completely for example?
Would we still need some kind of (currently missing) primitives "baked into" the Web API standards, and if so, perhaps which from the top of your head? I am really curious about that.

Thanks a lot for your time. Also I was under the impression those kind of "generic" questions didn't seem to fit the Github project's issues from what I remember but thanks a lot!!