-
Notifications
You must be signed in to change notification settings - Fork 776
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
PromiseClient is missing all the streaming methods #300
Comments
So please don't use it yet :) We are planning to work on this but unlikely to be available in the next quarter or so. |
Actually I'd like to use this thread as an API proposal discussion: What should a Promise-based API look like for streaming methods? |
I think Callback vs Promise is a debate for async request-response operations. Talking about streams of data, the Callback vs Promise doesn't make any sense. In fact, I think that there should be only promises and callbacks should die 🙂 In that sense, I'd question whether there should be 2 separate clients. It would be trivial to modify the existing generator so req-res calls return a promise by the default or use a callback if a callback is passed. |
Oh I think I misunderstood your original comment of "add stream calls to the PromiseClient" then. So you were saying that currently, in the undocumented About Callback vs Promise, I will punt on this argument for now :) |
Correct! My initial question was that the undocumented |
Yes a PR would be welcome :) Thanks! Sorry for the confusion. |
It seems that only Unary calls are added to the PromiseClient.
That means that, if you combine streaming and unary calls you either stick to the callback-based client or you need to have both clients.
Any reason for that? Would a PR to add stream calls to the PromiseClient be welcomed?
The text was updated successfully, but these errors were encountered: