Remove old Authentication code that we don't use or need.

remoting/protocol/connection_to_host.h

 // 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.
 
 #ifndef REMOTING_PROTOCOL_CONNECTION_TO_HOST_H_
 #define REMOTING_PROTOCOL_CONNECTION_TO_HOST_H_
 
 #include <string>
 
 #include "base/memory/ref_counted.h"
@@ skipping 30 matching lines @@
 class InputStub;
 class SessionConfig;
 class VideoReader;
 class VideoStub;
 
 class ConnectionToHost : public SignalStrategy::StatusObserver,
                          public SessionManager::Listener {
  public:
   enum State {
     CONNECTING,
+    // TODO(sergeyu): Currently CONNECTED state is not used and state
+    // is set to AUTHENTICATED after we are connected. Remove it and
+    // renamed AUTHENTICATED to CONNECTED?

[Wez, 2011/11/03 18:14:37]

With the EKE handshake in place we'll have a separation between "connected" and
"authenticated" again - we'll be accepting the session, then exchanging
authentication stanzas before we hook up the channels, during which time we're
connected but not authenticated?

I think it would make sense to call the
connected-and-authenticated-and-authorized state "connected", and to either have
an "authenticating" state after "connecting", or even to fold that into
"connecting".

[Sergey Ulanov, 2011/11/03 19:11:55]

I agree.

     CONNECTED,
     AUTHENTICATED,
     FAILED,
     CLOSED,
   };
 
   enum Error {
     OK,
     HOST_IS_OFFLINE,
     SESSION_REJECTED,
@@ skipping 110 matching lines @@
  private:
   DISALLOW_COPY_AND_ASSIGN(ConnectionToHost);
 };
 
 }  // namespace protocol
 }  // namespace remoting
 
 DISABLE_RUNNABLE_METHOD_REFCOUNT(remoting::protocol::ConnectionToHost);
 
 #endif  // REMOTING_PROTOCOL_CONNECTION_TO_HOST_H_