public-offering
/
pad.pub0.org
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Fixing a bug that happens when a socket.io connection closes very early after a CLIENT_READY message

pull/191/head
Peter 'Pita' Martischka 2011-10-19 21:48:36 +02:00
parent e0cf6098fb
commit 0f559347ee
1 changed files with 9 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
node/handler/PadMessageHandler.js
View File

@ -809,10 +809,15 @@ function handleClientReady(client, message)
//Send the clientVars to the Client //Send the clientVars to the Client
client.json.send(clientVars); client.json.send(clientVars);
//Save the revision and the author id in sessioninfos //sometimes the client disconnects very early and the session of it is already removed
sessioninfos[client.id].rev = pad.getHeadRevisionNumber(); //thats why we have to check that case
sessioninfos[client.id].author = author; if(sessioninfos[client.id] !== undefined)
{
//Save the revision and the author id in sessioninfos
sessioninfos[client.id].rev = pad.getHeadRevisionNumber();
sessioninfos[client.id].author = author;
}
//prepare the notification for the other users on the pad, that this user joined //prepare the notification for the other users on the pad, that this user joined
var messageToTheOtherUsers = { var messageToTheOtherUsers = {
"type": "COLLABROOM", "type": "COLLABROOM",