"409 Conflict" on joining a second time in the same conversation#3591

Merged

nickvergessen merged 22 commits intomasterfrom

bugfix/3415/conflict-on-joining-a-second-time

Jul 1, 2020

Commits on Jul 1, 2020

Optionally return 409 when trying to join a second time
nickvergessen
committed
Also support guests to prevent breaking their sessions
nickvergessen
committed
Return session id, in call flag and last ping
nickvergessen
committed
Always ask if we can join if we are not reloading the page
nickvergessen
committed
Ask for confirmation to join in case of session conflict
nickvergessen
committed
Automatically force join if the session is "old"
nickvergessen
committed
Add documentation for the conflict handling
nickvergessen
committed
Leave the room with the old session
nickvergessen
committed
Further pass on the sessionId to leaveRoomAsParticipant
nickvergessen
committed
Handle duplicated sessions more gracefully with the internal signaling
nickvergessen
committed
Better handle 404 error as well as all other undefined scenarios
nickvergessen
committed
Show session conflict warning when a session joins again for your own user
nickvergessen
committed
Redirect to a plain page to avoid reconnections
nickvergessen
committed
Send a signal to disconnect the old session before killing it
nickvergessen
committed
Don't show call state when asking to kill the other session
nickvergessen
committed
Trigger a vue event when SessionStorage "joined_conversation" changes
nickvergessen
committed
Don't kill the previous session when we navigate away
nickvergessen
committed
Handle the disinvite event properly when the session was kicked
nickvergessen
committed
Add a hack to check if the dialog was closed via the X
nickvergessen
committed
If the user has no participant anymore, it was not a conflict
nickvergessen
committed
Fix mixin state also when the component is loaded after the state already changed
nickvergessen
committed
Update the session and the call flag when force joining
nickvergessen
committed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

"409 Conflict" on joining a second time in the same conversation#3591

"409 Conflict" on joining a second time in the same conversation#3591
nickvergessen merged 22 commits intomasterfrom
bugfix/3415/conflict-on-joining-a-second-time

Commits on Jul 1, 2020

Optionally return 409 when trying to join a second time

Also support guests to prevent breaking their sessions

Return session id, in call flag and last ping

Always ask if we can join if we are not reloading the page

Ask for confirmation to join in case of session conflict

Automatically force join if the session is "old"

Add documentation for the conflict handling

Leave the room with the old session

Further pass on the sessionId to leaveRoomAsParticipant

Handle duplicated sessions more gracefully with the internal signaling

Better handle 404 error as well as all other undefined scenarios

Show session conflict warning when a session joins again for your own user

Redirect to a plain page to avoid reconnections

Send a signal to disconnect the old session before killing it

Don't show call state when asking to kill the other session

Trigger a vue event when SessionStorage "joined_conversation" changes

Don't kill the previous session when we navigate away

Handle the disinvite event properly when the session was kicked

Add a hack to check if the dialog was closed via the X

If the user has no participant anymore, it was not a conflict

Fix mixin state also when the component is loaded after the state already changed

Update the session and the call flag when force joining