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

Handle Server Dropouts using authorized tags cache #3

Open

nog3 opened this issue Oct 14, 2018 · 0 comments

Labels

enhancement high priority

Member

nog3 commented Oct 14, 2018

Related to #2

If the server doesn't respond to a heartbeat the client should:

Set a flag to start using the local authorized tags cache.
Load the tags cache into RAM from authorised.json

When the server responds to a heartbeat, the client should:

Make sure the flag for using the local authorized tags cache is not set.
Unload the tags cache from RAM, if it's there.

When the server doesn't respond to an auth request for a tag, the client should:

Load the tags cache into RAM from authorised.json
Check against the tags cache for the current user and auth based on that.
Set a flag to start using the local authorized tags cache.

Ideally the enabling cache during auth won't happen, due to a default 1 minute heartbeat.

jabelone added enhancement high priority labels

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment