-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
ManagedChannel getState/notifyChanged API docs #3762
Comments
We don't own all implementations of ManagedChannel, so we cannot be certain all implementations do. The only known implementation, ManagedChannelImpl, does implement it. Using ManagedChannelBuilders written by the gRPC team will implement these methods. |
Understood, but the docs still say it's not implemented and have links to closed issues ( #28 and #2292 ).
That's the main thing that threw me for a loop. Maybe a forward reference to |
@dapengzhang0 Do you know if the Channel state APIs are complete an implemented everywhere? Can the warning be removed? |
The warning should be removed since the API is implemented in the main impl of |
ManagedChannel now supports the getState/notifyWhenStateChanged API (grpc#2292).
ManagedChannel now supports the getState/notifyWhenStateChanged API (#2292).
ManagedChannel now supports the getState/notifyWhenStateChanged API (grpc#2292).
Fixed by #3768 |
ManagedChannel now supports the getState/notifyWhenStateChanged API (#2292).
I'm using gRPC 1.7 (on Android) and notice the docs for
ManagedChannel
still say this functionality is unimplemented (and the base implementation throws as it should). However, theMannagedChannelImpl
(whichOkHttpChannelImpleBuilder
uses) has this implemented. Is this an oversight or on purpose? It caused me to dive into the issues (culminating in #2292) to figure out if this was actually supported yet (I've determined it is). Should the docs be updated to something a little more helpful?The text was updated successfully, but these errors were encountered: