From 83407ab4df474155030bddac706edeabb0567c57 Mon Sep 17 00:00:00 2001
From: John McLear <john@mclear.co.uk>
Date: Wed, 3 Apr 2013 02:58:11 +0100
Subject: [PATCH] so it turns out the timeslider socket cant access anything

---
 src/node/handler/SocketIORouter.js | 13 ++++++++++++-
 1 file changed, 12 insertions(+), 1 deletion(-)

diff --git a/src/node/handler/SocketIORouter.js b/src/node/handler/SocketIORouter.js
index 483bb1d17..0ab0d9b00 100644
--- a/src/node/handler/SocketIORouter.js
+++ b/src/node/handler/SocketIORouter.js
@@ -107,16 +107,27 @@ exports.setSocketIO = function(_socket)
       else
       {
         //this message has everything to try an authorization
+if(message.type == "COLLABROOM"){
+  console.warn("message1", message)
+  // pad if is fine
+  // sessionid is not set
+  // message.token is not set
+  // message.password is undefined..
+}
         if(message.padId !== undefined && message.sessionID !== undefined && message.token !== undefined && message.password !== undefined)
         {
+if(message.type == "COLLABROOM"){
+  console.warn("yaymessage", message); // I get here..
+}
           securityManager.checkAccess (message.padId, message.sessionID, message.token, message.password, function(err, statusObject)
           {
             ERR(err);
-            
+            console.warn("here too", statusObject);
             //access was granted, mark the client as authorized and handle the message
             if(statusObject.accessStatus == "grant")
             {
               clientAuthorized = true;
+// console.warn("handling message");
               handleMessage(message);
             }
             //no access, send the client a message that tell him why