Cleanup output, trap exceptions, timing output, fixes.

Fixes:
- Make sure that failed state messages stay around until next connect.
- Get status message font colors working.
- Clear RQ_reorder list on re-connect.

README.md

@@ -36,7 +36,7 @@ There a few reasons why a proxy is required:
      strings (Unicode encoding messes with it) even though you can
      read them with WebSocket. The python proxy encodes the data so
      that the Javascript client can base64 decode the data into an
-     array. The client requests this encoding
+     array.
 
   3. When using the web-socket-js as a fallback, WebSocket 'onmessage'
      events may arrive out of order. In order to compensate for this

canvas.js

@@ -51,7 +51,7 @@ ctxDisable: function (e) {
 
 
 init: function (id, width, height, keyDown, keyUp, mouseDown, mouseUp, mouseMove) {
-    console.log(">> init_canvas");
+    console.log(">> Canvas.init");
 
     Canvas.id = id;
 
@@ -84,7 +84,7 @@ init: function (id, width, height, keyDown, keyUp, mouseDown, mouseUp, mouseMove
     
     Canvas.prevStyle = "";
 
-    console.log("<< init_canvas");
+    console.log("<< Canvas.init");
 },
 
 clear: function () {

wsproxy.py

@@ -56,7 +56,7 @@ def do_proxy(client, target):
             sent = client.send(dat)
             if sent == len(dat):
                 traffic("<")
-                ##log.write("Client send: %s\n" % repr(dat))
+                ##log.write("Client send: %s ...\n" % repr(dat[0:80]))
             else:
                 cqueue.insert(0, dat[sent:])
                 traffic("<.")