Propagate connection state from networking layer to UI.

remoting/protocol/connection_to_host.cc

Index: remoting/protocol/connection_to_host.cc
diff --git a/remoting/protocol/connection_to_host.cc b/remoting/protocol/connection_to_host.cc
index 5794c50216f15daff92d3da49b1890f40c3e2612..16893dd19c5d23d2b2906c67e0c53268674bb0d0 100644
--- a/remoting/protocol/connection_to_host.cc
+++ b/remoting/protocol/connection_to_host.cc
@@ -209,6 +209,12 @@ void ConnectionToHost::OnSessionRouteChange(const std::string& channel_name,
                                             const TransportRoute& route) {
 }
 
+void ConnectionToHost::OnSessionInactive(const std::string& channel_name,
+                                         bool inactive) {
+  if (channel_name == kVideoChannelName)
+    event_callback_->OnConnectionInactive(inactive);

[Wez, 2012/07/16 18:51:23]

You're basing the connection's "active" state purely on whether the video
channel is active; although it's the highest throughput channel, it's equally
disruptive for the event channel not to be "active", and if the web-app knew
that the event channel were inactive it could provide some transient indicator
of the fact in the UI. If you expose the list of "active" channels to the app in
each notification then you can provide more fine-grained indicators; otherwise,
include the states of all channels in the single session-active indication?

[Sergey Ulanov, 2012/07/17 01:17:17]

Changed it to set ready=false when any of the channels is not ready.

+}
+
 ConnectionToHost::State ConnectionToHost::state() const {
   return state_;
 }