Isthereanywaytocircumventthebrowserslimitationsforconcurrentconnectionshttp2

Hi there,

after hours of reading and getting stuck in a cycle of always the same web search results without ever getting a clear statement or solution I decided to open a request for clarification here.

I found those:

https://github.com/grpc/grpc-web/issues/432 --> no proxy used

and

https://github.com/grpc/grpc-web/issues/81 --> nginx related, what to do with envoy?

which seem to be nearest to my question, but.. I don't get it.

So, from scratch: we're using grpc web for our browser client, envoy as proxy and some grpc backend services.

We have in our application many oneToMany (take for example stock prices) subscriptions. Chrome handles 6 server streaming requests and that's it. From my understanding, grpc-web can use http/2 transport with some grpc protocol differences. Chrome should be using http/2 transport cause it supports it (?), but it doesn't. This way I'm limited to 6 open server streams which is literally nothing.

What am I missing? And whats the point in grpc web GA when it's not really usable in web clients?

Hope someone can bring some light into the dark...

Greetings,
Maik

该提问来源于开源项目：grpc/grpc-web