A new authenticated connection evicts an old one.

remoting/protocol/host_message_dispatcher.h

Index: remoting/protocol/host_message_dispatcher.h
diff --git a/remoting/protocol/host_message_dispatcher.h b/remoting/protocol/host_message_dispatcher.h
index 60afb276bf1a12ab59c35c42798304bf4966878b..a3c1cd56539ab858431b420f29d13dedef670fdc 100644
--- a/remoting/protocol/host_message_dispatcher.h
+++ b/remoting/protocol/host_message_dispatcher.h
@@ -1,4 +1,4 @@
-// Copyright (c) 2010 The Chromium Authors. All rights reserved.
+// Copyright (c) 2011 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
@@ -13,6 +13,7 @@
 namespace remoting {
 namespace protocol {
 
+class ConnectionToClient;
 class ControlMessage;
 class EventMessage;
 class HostStub;
@@ -37,7 +38,7 @@ class HostMessageDispatcher {
 
   // Initialize the message dispatcher with the given connection and
   // message handlers.
-  void Initialize(protocol::Session* session,
+  void Initialize(ConnectionToClient* connection,
                   HostStub* host_stub, InputStub* input_stub);
 
  private:
@@ -61,6 +62,8 @@ class HostMessageDispatcher {
   // They are called on the thread there data is received, i.e. jingle thread.
   HostStub* host_stub_;
   InputStub* input_stub_;
+
+  ConnectionToClient* connection_;

[Sergey Ulanov, 2011/03/18 18:12:21]

With this change, HostMessageDispatcher hold reference to ConnectionToClient,
and ConnectionToClient holds reference to HostMessageDispatcher. That is not
good, and I would like to avoid this pattern if possible,

[simonmorris, 2011/03/22 13:09:10]

Done.

 };
 
 }  // namespace protocol