Skip to content
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

Add overrideAuthority for Channel construction #997

Merged
merged 4 commits into from
Sep 11, 2015

Conversation

ejona86
Copy link
Member

@ejona86 ejona86 commented Sep 10, 2015

For #925

@@ -64,7 +64,7 @@
* The authority of the destination this channel connects to. Typically this is in the format
* {@code host:port}.
*
* @return authority of remote, or {@code null}
* @return authority of remote
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: maybe just remove the @return altogether? It's duplicating the docs.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done.

@nmittler
Copy link
Member

@ejona86 LGTM

Although the functionality is currently available by passing a
manually-created InetAddress, that requires that the user do I/O before
calling our API and does not work with naming in the future.
We want to allow overriding authority in the ManagedChannelBuilder for
testing. In doing that, we basically require that all Channels support
authority. In reality, this simplifies things and is already being done
by the C implementation, as their unix domain socket support uses
"localhost" just like our in-process transport now does.

We can debate some whether "localhost" is really the most appropriate
authority for the in-process transport, but that should probably happen
later since "localhost" is "good enough" for now.
@ejona86 ejona86 merged commit bccaf07 into grpc:master Sep 11, 2015
@ejona86 ejona86 deleted the override-authority branch September 11, 2015 16:44
@lock lock bot locked as resolved and limited conversation to collaborators Jan 22, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants