-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
client receives all the messages at once when using server-side streaming? #60
Comments
It works for me, the client receives the messages separately, when pushed from the server. (Not on connection close) Tested on:
|
This all depends on what client implementation you are using. If this issue persists try to contact the client library maintainers |
Thanks for the answers, I am not sure what you mean by client implementation? could you elaborate more? I am following your example @smnbbrv and it's still not working for me. my code is using grpc-web-client. maybe my Envoy setup is not correct? (I am also taking this from existing examples) |
By client implementation I mean packages grpc-web or @improbable-eng/grpc-web . This project is just a middleware that is adapted for these libs with corresponding packages. The connection itself is implemented by the client lib and issues there are very hard to debug. It is almost impossible to say what is particularly wrong in your implementation without seeing and debugging the whole project and infrastructure; and, as being said above, is not a subject of ngx-grpc. If you however will be able to find the issue on this side, it should be fixed of course. |
As long as the issue is not active anymore I close it. Please feel free to reopen in case it can be reproduced |
Hi, I was wondering if that's still a expected behavior I am seeing?
client receives all the messages at once when using server-side streaming
I noticed this feature was a WAI back in 2019
https://grpc.io/blog/state-of-grpc-web/#f20
I was wondering if this is still not supported?
The text was updated successfully, but these errors were encountered: