grpc-java/core/src
Kun Zhang e875a8c6a3
core: introduce NameResolver.Helper and deprecate the params on newNameResolver() (#5345)
Context: [#4159 (comment)](https://github.com/grpc/grpc-java/issues/4159#issuecomment-415827641)

`Attributes` is appropriate for plumbing optional objects, especially useful for a long plumbing path where components in the middle may not care or see all objects in the container. It's not the case for the `params` on `newNewResolver()`. Both the default port and the proxy detector are guaranteed to be there and the plumbing path is very short. In this case, a first-class object is more appropriate and easier to use.

The `Helper` will also have `getSynchronizationContext()` (#2649) and a method to parse and validate service config. We we also considering merging `Listener` into the `Helper`, to make `NameResolver` match the `LoadBalancer` API.
2019-02-12 10:14:59 -08:00
..
bazel-internal/resources/META-INF/services core: fix bazel NameResolverProvider not found 2018-12-05 09:45:41 -08:00
bazel-util/resources/META-INF/services core: fix bazel NameResolverProvider not found 2018-12-05 09:45:41 -08:00
jmh/java/io/grpc all: remove java6 type args 2019-02-04 10:03:50 -08:00
main core: introduce NameResolver.Helper and deprecate the params on newNameResolver() (#5345) 2019-02-12 10:14:59 -08:00
test core: introduce NameResolver.Helper and deprecate the params on newNameResolver() (#5345) 2019-02-12 10:14:59 -08:00