Reload the web-app if an IT2Me connection fails.

remoting/webapp/client_screen.js

Index: remoting/webapp/client_screen.js
diff --git a/remoting/webapp/client_screen.js b/remoting/webapp/client_screen.js
index 4e1952dc36b6f8e97c15548320d6c09978f2d874..377f4cb7dd64bfe2037a6f66ff5a682ded19cbe0 100644
--- a/remoting/webapp/client_screen.js
+++ b/remoting/webapp/client_screen.js
@@ -136,6 +136,7 @@ function onClientStateChange_(oldState, newState) {
       showConnectError_(remoting.Error.MISSING_PLUGIN);
       break;
   }
+  remoting.clientSession.disconnect(false);
   remoting.clientSession.removePlugin();
   remoting.clientSession = null;
 }
@@ -159,10 +160,6 @@ function showConnectError_(errorTag) {
   } else {
     remoting.setMode(remoting.AppMode.CLIENT_CONNECT_FAILED_ME2ME);
   }
-  if (remoting.clientSession) {
-    remoting.clientSession.disconnect(false);
-    remoting.clientSession = null;
-  }

[Jamie, 2013/02/14 01:13:33]

The only case where showConnectError is called with clientSession non-NULL is
from onClientStateChange_. Moving this code there makes more sense, as
disconnecting is not an obvious side-effect of showing an error message.

 }
 
 /**