mirror of
https://github.com/nextcloud/talk-android.git
synced 2024-11-23 21:45:42 +03:00
Do not store sessions not in call as old sessions
The old sessions are used to know which connections need to be ended because they are no longer in the call. However, if a participant is no longer in the call but there was no connection yet then there is no connection that needs to be ended; any existing connection will be added when looping through the connection list, and if it needs to be stopped it will be found when substracting the sessions that are currently in the call. The old sessions are also used to find the new sessions in the call. Due to an issue in how that is computed "newSessions" currently store the sessions in the call rather than only the new sessions (this will be addressed in a following commit). Nevertheless, in both cases any session not in the call for which there is no connection either will not make any difference in the computed "newSessions" (as they are mutually exclusive, so they will never be removed from "newSessions" when substracting the old sessions). Due to all that it is not needed to store sessions not in call as old sessions / sessions to end. Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
This commit is contained in:
parent
1ba6e293b2
commit
f84a621780
1 changed files with 0 additions and 2 deletions
|
@ -1859,8 +1859,6 @@ public class CallActivity extends CallBaseActivity {
|
|||
boolean isInCall = inCallFlag != 0;
|
||||
if (isInCall) {
|
||||
newSessions.add(participant.get("sessionId").toString());
|
||||
} else {
|
||||
oldSessions.add(participant.get("sessionId").toString());
|
||||
}
|
||||
|
||||
// The property is "userId" when not using the external signaling server and "userid" when using it.
|
||||
|
|
Loading…
Reference in a new issue