Skip to content

Conversation

@ST-DDT
Copy link
Contributor

@ST-DDT ST-DDT commented Dec 8, 2019

The dns scheme is only the default scheme with grpc-java. Other
libraries could add more NameResolvers and thus change the default. For
compatibility reasons, the schema should therefore be specified
explicitly.

The current javadocs conflict with those of NameResolverProdiver#priority(), which allow setting a priority higher than DNS.

Users of grpc-spring-boot-starter who want to use a service discovery have the problem that many libraries don't provide a schema for DNS addresses and therefore don't work anymore without additional configuration.

https://github.com/yidongnan/grpc-spring-boot-starter/issues/268
https://github.com/yidongnan/grpc-spring-boot-starter/issues/304
https://github.com/yidongnan/grpc-spring-boot-starter/issues/300

The dns scheme is only the default scheme with grpc-java. Other
libraries could add more NameResolvers and thus change the default. For
compatibility reasons, the schema should therefore be specified
explicitly.
@dapengzhang0
Copy link
Contributor

Users of grpc-spring-boot-starter who want to use a service discovery have the problem that many libraries don't provide a schema for DNS addresses and therefore don't work anymore without additional configuration.
yidongnan/grpc-spring-boot-starter#268
yidongnan/grpc-spring-boot-starter#304
yidongnan/grpc-spring-boot-starter#300

@ejona86

@ejona86 ejona86 requested a review from dapengzhang0 December 16, 2019 23:34
@ejona86 ejona86 added the kokoro:run Add this label to a PR to tell Kokoro the code is safe and tests can be run label Dec 16, 2019
@grpc-kokoro grpc-kokoro removed the kokoro:run Add this label to a PR to tell Kokoro the code is safe and tests can be run label Dec 16, 2019
@ejona86 ejona86 merged commit 2afe134 into grpc:master Dec 16, 2019
@ejona86
Copy link
Member

ejona86 commented Dec 16, 2019

Thank you!

@ST-DDT ST-DDT deleted the adjust-javadocs branch December 17, 2019 09:29
@lock lock bot locked as resolved and limited conversation to collaborators Mar 17, 2020
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.

4 participants