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

Alternative client (httpx) support #232

Closed
johtso opened this issue Sep 19, 2020 · 0 comments
Closed

Alternative client (httpx) support #232

johtso opened this issue Sep 19, 2020 · 0 comments

Comments

@johtso
Copy link

johtso commented Sep 19, 2020

I've been exploring async http client options and in the process have found that by leaving requests+CacheControl behind, there seemed to be no options that provided ETag based caching.

In order to get caching functionality with httpx, which seems like one of the most solid async clients at the moment, it looks like all that would be needed is a Transport.

Would making this project more client agnostic be a reasonable goal?

From a brief look around it seems like there are a couple of places outside of adapter.py that requests is imported, and requests is currently required in setup.py
Thoughts?

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

No branches or pull requests

1 participant