Better sessions in oauth example #3299
Open
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.
Updates the oauth example to use a better approach to session management.
Motivation
The current approach to sessions within the oauth example is not fit for any circumstance, and if anyone where to take it at face value and use
async_sessions
their application would encounter severe performance issues. The current approach not only fails to lead users down the right path but actively leads them down the wrong path.Solution
By updating the example to use a viable approach it helps people understand the right way to solve the problem, rather than potentially misleading them.