Don't transition to in-session mode until the connection has been established.

remoting/webapp/me2mom/choice.html

Index: remoting/webapp/me2mom/choice.html
diff --git a/remoting/webapp/me2mom/choice.html b/remoting/webapp/me2mom/choice.html
index 956a0d1af97b0594bb669b0ee73cbe02f04c8144..5c83ccac18c8afbfb566f250393479e4906b55e3 100644
--- a/remoting/webapp/me2mom/choice.html
+++ b/remoting/webapp/me2mom/choice.html
@@ -239,7 +239,7 @@ found in the LICENSE file.
       </footer>
     </section> <!-- choice-mode -->
 
-    <section id="session-mode" class="mode in-session-element">
+    <section id="session-mode" class="mode in-session-element client-element">

[Jamie, 2011/07/25 23:09:50]

The plugin has to be visible in order for it to load, which we now want to
happen before the state transition.

[awong, 2011/07/26 18:51:27]

Hmm...I wonder if we ever want it to not load.  I guess it takes up more
resources.

[Jamie, 2011/07/26 19:02:35]

I'm not sure I understand your point. We wouldn't want it to load in host mode,
for example, and if a second client connection is made, we want to tear down the
first plugin and recreate it, so we need the on-demand creation semantics.

     </section> <!-- session-mode -->