Skip to content

Conversation

AgeManning
Copy link
Member

Description

Users cannot keep track of active sessions as they expire internally in our cache. This PR adds an extra message (breaking the API), that reports when a session has been removed from our internal cache.

This does change the expiry logic also. Previously we were removing elements on most operations, i.e when we send/receive a message. We now only remove old elements when a new session is added, or one fails. So long as there are new connections, we will expire old ones. If the peer set remains consistent without errors, we will no longer expire elements simply based on time. I don't consider this an issue (we can also add this functionality back if anyone is concerned about checking the cache more regularly).

Copy link
Contributor

@KolbyML KolbyML left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:shipit: looks good that you for resolving this for us so quick 🔥

@ackintosh
Copy link
Member

Looks good to me.

@AgeManning AgeManning merged commit b92b6c9 into master Sep 15, 2025
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants