Wenbo Zhu

We did a lengthy Chrome origin-trail from Q2-4/21 to test if streaming POST would work over HTTP/1.1, using Google's end-user facing traffic (gmail etc). Unfortunately the results are inconclusive. The...

@mhoad Sorry that we haven't been making much progress on this, with a very small team working on both opensource and google-internal features. What I believe will benefit developers is...

Sorry for the delayed response. We are happy to get any contribution on this. Our current plan to handle grpc-web traffic using Servlet APIs and then proxy the traffic to...

@johanbrandhorst Thanks for the point. We are in the process of launching grpc-web as an alpha release, and will publish the plan on bidi support (road-map) after Q2.

@HTChang no, the grpc-web repo version doesn't support bidi streaming. We probably should add a comment to the proto too to avoid confusion. @stanley-cheung

We don't yet have a future-proof transport story that allows us to provide cross-browser support and at same time serve both OSS and internal users. Will publish the road-map doc...

Thanks for reading the ROADMAP. This [slide deck](https://cdn.oreillystatic.com/en/assets/1/event/214/From%20WebSockets%20to%20WiSH%20_web%20in%20strict%20HTTP_%20Presentation.pdf) talked about websockets v.s. pure HTTP, with some stats from chrome. We understand the desire to design a single API that works...

Re: websockets, we would welcome all the gateways that provide inter-operability with gRPC end-points. WS over HTTP/2 is being finalized and will be available in Chrome. We will evaluate if...

grpc-web does intend to support important browser use cases, i.e. features, versions, environments etc ... and the current spec is implementation details but important. I don't necessarily agree tunneling grpc/http2...

fixed it.