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

Fallback to cache when connection is lost #22

Open
hannesrichter opened this issue Apr 27, 2021 · 1 comment
Open

Fallback to cache when connection is lost #22

hannesrichter opened this issue Apr 27, 2021 · 1 comment
Assignees
Labels
enhancement New feature or request question Further information is requested

Comments

@hannesrichter
Copy link
Member

When using a proxy pool, the runtime should enable an optional fallback to locally cached objects for uninterrupted execution if the network connection to the API is lost.

@hannesrichter hannesrichter added the enhancement New feature or request label Apr 27, 2021
@jonau jonau self-assigned this May 3, 2021
@jonau jonau added the question Further information is requested label May 3, 2021
@jonau
Copy link
Member

jonau commented May 3, 2021

there are a few questions we have to clarify first:

  1. How do we detect that we don't have a network connection. I think it is only detectable either by a refused connection or a timeout (would that be configurable?).
  2. The last option would mean, that we always need to wait for a possible network response, which would slow down the execution. Is this acceptable?

Maybe we should introduce a "offline mode" that is either activated by a connection error, or by the configuration. We try to reconnect at each request(except when it we force the offline mode) but immediately return the cached object. As soon as we get a valid response we switch back to "normal mode"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants