-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Optimize Fabric deletion and destroy sessions #251
Conversation
@@ -119,7 +119,13 @@ export const OperationalCredentialsClusterHandler: (conf: OperationalCredentials | |||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Removing session associated with a fabric when a fabric is deleted should be done by the FabricManager, otherwise there is too much risk to have the system in an incoherent state.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I moved it to "MatterDevcie" now because FabricManager do not have acces to the session controller but the device is taling care here too ... so should work?
ALternatively Ineed to pass the sessionmanager with removeFabric justto call from there ...
@mfucci COmments addressed ... one topic basically open - see above, but I did a change to where it also could make sense in my eyes. Ready for re-review |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's make sure the system cannot fall in an incorrect state
@mfucci Adjusted as discussed |
When a Fabric gets deleted the current session associated with the Fabric needs to be destroyed. If it is the last fabric all other remaining sessions also needs to be destroyed