FIX: Session_Manager::find_all() is inefficient #3451
Merged
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.
Now that we're talking about the efficiency of the
Session_Manager
class hierarchy: This is likely something that should go in before the release candidate. It replacesSession_Manager::find_all()
with::find_some()
.Technically, nothing would have forced application-defined session managers to actually always return "all" found sessions, but the method name very much implied that. Instead, it is now called
find_some()
and gets a "max sessions hint" that implementations can (and should) follow.Additionally, the
Session_Manager
base class now has some mechanics to callfind_some()
more than once if the returnedSession
objects don't pass its filters -- currently mainly a session expiry check. This algorithm might see some evolution, but I think thefind_some()
interface is more versatile and better suited.