fix: removeUser - handle connections in frontends, db changes in backend #12695
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.
What does this PR do?
Reorganized the handling of
UserLeftMeetingEvtMsg
by bbb-html5 so that the backends handle processing to update MongoDB and the frontends handle processing to update the ClientConnections. This way there's no overlap/unpredictabilitysplit the handling of logic for UserLeft message - backend handles the updates for Mongo, frontend handles the updates to ClientConnections
removed the 1 second delay since now only backend handles the userleft+user ejected messages and they are syncronous
no longer initialize ClientConnections on backend instances
Closes Issue(s)
Closes #12080 since we are now guaranteed to be processing sequentially the two relevant events in a single NodeJS instance:
Motivation
We were looking into ways to remove the 1000 ms delay added in #12057 and particularly why the re-ordering of events processing was happening.