diff options
| author | Daniel Calviño Sánchez <danxuliu@gmail.com> | 2020-05-18 04:22:34 +0300 |
|---|---|---|
| committer | Daniel Calviño Sánchez <danxuliu@gmail.com> | 2020-05-19 06:09:44 +0300 |
| commit | 533bd5fc04cc0adf224a88b540be7c49757f2742 (patch) | |
| tree | d674b275b68b5924ed444ec3b7e479a2aa37a0fc /src/utils/signaling.js | |
| parent | fb4191e5bcbe3cc3ad99f27a16023412671d8ed9 (diff) | |
Do not fetch all conversations on room participants update events
The room participants update events are sent by the external signaling
server:
-When a user resumes the session
-When an internal client joins or leaves the conversation
-When the BackendNotifier sends a "participants" event (that is, when
the type of a participant changes, when the name of a guest changes or
when guests are cleaned)
-When the BackendNotifier sends a "incall" event (that is, when a
participant joins or leaves the call)
In all those cases it is not really needed to fetch all the
conversations to get the updated state, but only the current
conversation. Note that it is not enough to fetch just the participants,
as for example when a call is started that modifies some attributes in
the conversation, like "hasCall".
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
Diffstat (limited to 'src/utils/signaling.js')
| -rw-r--r-- | src/utils/signaling.js | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/src/utils/signaling.js b/src/utils/signaling.js index 2791b9c3a..0c48c817a 100644 --- a/src/utils/signaling.js +++ b/src/utils/signaling.js @@ -1074,7 +1074,6 @@ Signaling.Standalone.prototype.processRoomParticipantsEvent = function(data) { case 'update': this._trigger('usersChanged', [data.event.update.users || []]) this._trigger('participantListChanged') - EventBus.$emit('shouldRefreshConversations') break default: console.error('Unknown room participant event', data) |