feat(http): introduce session cleanup strategies#2068
Open
Conversation
Benchmark ResultsComparison of Open to see the benchmark results
Generated by phpbench against commit 516412c |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Closes #2061
This pull request refactors session clean up to allow the choice between cleaning up sessions after every request (the current behavior), cleaning up session after random requests (2/100 chance), or disabling session cleanup in favor of a schedule-based clean up.
The database session installer has been removed in favor of a session installer, which allows choosing a driver (file, redis, database), and allows specifying the clean up strategy (except if Redis is chosen). When the session cleanup is disabled, the installer suggests installing the scheduled cleaning up command.