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

Support multiple network interfaces #1780

Closed
swankjesse opened this issue Aug 1, 2015 · 1 comment
Closed

Support multiple network interfaces #1780

swankjesse opened this issue Aug 1, 2015 · 1 comment
Labels
enhancement Feature not a bug
Milestone

Comments

@swankjesse
Copy link
Collaborator

In particular, we want to:

  • Allow an OkHttpClient instance to be pinned to a specific network interface (ie. source IP address). For example, pinning to the WiFi interface would cause it to use that interface for both DNS and connections. Nothing would fall back to the cellular radio.
  • Be smarter when no network is pinned. If the device's network changes, we may need to clear the connection pool!
@swankjesse
Copy link
Collaborator Author

With the DNS change and pluggable socket factories I think we cover these use cases well enough. Might be worth reconsidering the API for OkHttp 3, but that'll be a separate effort.
#1967

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Feature not a bug
Projects
None yet
Development

No branches or pull requests

2 participants