You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
MQTT 5 allows session expiration, so at some point if someone decides to move ahead with implementation, the persistence modules will need some work done. At present I'm considering incorporating it into a MQTT 5 server I've been working on.
What would the roadmap be for this to happen, would the work have to start with aedes-cached-persistence, or would it have start with the individual persistences?
As an alternate, I suppose a person could do a plugin similar to the way the aedes-stats plugin works, but that may be problematic if the internals of the persistences change.
The way I'd see it, it could be separate api calls, or integrated, but essentially I'd be thinking something like:
sessionStart(clientId)
sessionRefresh(clientId) // Reset the session expiration
expiredSessions() // the broker would clear expired sessions based on returned items (client and client:* keys)
For redis I'm thinking about using a sorted set with value = clientId, score = expiration.
The text was updated successfully, but these errors were encountered:
This needs to be implemented on aedes-persistence first and then aedes-cached-persistence and at last on all other persistences. The plugin way isn't good IMO
MQTT 5 allows session expiration, so at some point if someone decides to move ahead with implementation, the persistence modules will need some work done. At present I'm considering incorporating it into a MQTT 5 server I've been working on.
What would the roadmap be for this to happen, would the work have to start with aedes-cached-persistence, or would it have start with the individual persistences?
As an alternate, I suppose a person could do a plugin similar to the way the aedes-stats plugin works, but that may be problematic if the internals of the persistences change.
The way I'd see it, it could be separate api calls, or integrated, but essentially I'd be thinking something like:
For redis I'm thinking about using a sorted set with value = clientId, score = expiration.
The text was updated successfully, but these errors were encountered: