Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Starting on audit recommendations. The following are implemented
For allowing sessions to be shared between server workers the only real in-memory solution I can find seems to be using Redis.
This requires a Redis server to be set up in the background and currently I am just pickling entire Sessions for every API call.
Redis could also provide solutions for rate limiting and session cleanup which I will look into if we decide to move forward with Redis.
TODO assuming we move forward with Redis:
The only other solutions I can think of for sharing sessions among workers is some kind of database. Redis, being in-memory, should be faster.