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
This is an important part of room lifecycle management.
Spec states that
(CHA-RL7a) [Testable] Room lifecycle operations have a precedence. If multiple operations are scheduled to run, they run in the following order:
(CHA-RL7a1) The RETRY operation – an internal process.
(CHA-RL7a2) The RELEASE operation.
(CHA-RL7a3) The ATTACH and DETACH operations have equal precedence
We have currently specified two solutions for this
I have listed few concerns with option 1, since it needs extra implementation to handle edge cases and can cause memory leaks even after room release.
So, currently going with option 2, I have raised channel attach PR on top of it -> [ECO-5009][CHA-RL1] Roomlifecycle Attach with retry #33. We can refactor it a bit more, but I strongly believe the current impl. is well-tested and can be used as a part of the room lifecycle
(CHA-RL7a) [Testable] Room lifecycle operations have a precedence. If multiple operations are scheduled to run, they run in the following order:
(CHA-RL7a1) The RETRY operation – an internal process.
(CHA-RL7a2) The RELEASE operation.
(CHA-RL7a3) The ATTACH and DETACH operations have equal precedence
┆Issue is synchronized with this Jira Task by Unito
The text was updated successfully, but these errors were encountered: