Any reason why CronetBuilder doesn't allow custom nameResolverProvider?

[jchau207]

Any reason why CronetBuilder doesn't allow custom nameResolverProvider?

[ejona86]

Cronet uses the DNS client built into Cronet, so it disables the normal name resolution. Are you needing custom name resolution for Cronet?

[jchau207]

Cronet uses the DNS client built into Cronet, so it disables the normal name resolution. Are you needing custom name resolution for Cronet?

Yes, we have a custom name resolver that uses cloudflare dns service instead Google's. It is more performant from our testing.

[ejona86]

The custom name resolver is faster than cronet's, or 1.1.1.1 is faster than 8.8.8.8? I'd expect cronet to be using the device's configured dns server.

Is your app gRPC-only, or does it do any plain HTTP? In mixed apps, there is value in using plain cronet, as you only pay DNS lookup and connection establishment costs once.

Cronet handles TLS and is only given a URL to contact, so it isn't really possible to specify IP addresses from within gRPC. You might take a look at CronetEngine.Builder for some of the options it offers, but I'm not seeing anything off-the-top that looks powerful enough for what you need.

[jchau207]

We see 1.1.1.1 being faster than 8.8.8.8.

In terms of communicating with our backend, our app is grpc-only.

I noticed there is a DNS option in the documentation, but I can't access it with the coronet engine builder from the grpc package io.grpc:grpc-cronet. Is the coronet builder in io.grpc, a customized builder?

[ejona86]

but I can't access it with the coronet engine builder from the grpc package io.grpc:grpc-cronet

What documentation? You pass a CronetEngine to the grpc builder, so you are in full control of Cronet's configuration to whatever extent that is possible.

[ejona86]

Seems like we've answered this as much as we can. All I/O within the scope of Cronet itself. If not and we missed something, comment, and it can be reopened.