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.

Sign up for GitHub

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

Jump to bottom

On retry: force use of a fresh connection #201

Closed
sosthene-nitrokey opened this issue Aug 12, 2024 · 2 comments
Closed

On retry: force use of a fresh connection #201

sosthene-nitrokey opened this issue Aug 12, 2024 · 2 comments

Comments

@sosthene-nitrokey
Copy link
Contributor

I think this can be done by simply dropping the ureq::Agent and recreating one on the fly.

We might have to use arc_swap to be able to change the client without having a mutex.
@jans23 jans23 mentioned this issue Sep 11, 2024
Closed
@sosthene-nitrokey
Copy link
Contributor Author

TODO:

  • Ureq: add connection pool clear method
  • On IO failure: clear all the pools of all the instances

@sosthene-nitrokey
Copy link
Contributor Author

Done by #218

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@sosthene-nitrokey