Remove AccessVerifier interface.

remoting/host/access_verifier.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_HOST_ACCESS_VERIFIER_H_
 #define REMOTING_HOST_ACCESS_VERIFIER_H_
 
 #include <string>
 
 #include "base/basictypes.h"
 
 namespace remoting {
 
 // AccessVerifier is used by ChromotingHost to verify that access to
 // the host. There are two implementations: SelfAccessVerifier is used
 // in the Me2Me scenario, SupportAccessVerifier is used for Me2Mom.

[Wez, 2011/11/23 01:23:04]

Presumably SupportAccessVerifier is no longer required?

 class AccessVerifier {

[Wez, 2011/11/23 01:23:04]

Why do we still need this interface?  Can't we apply this access control in
Authenticator implementations?

[Sergey Ulanov, 2011/11/23 21:18:46]

We may still need something like it later, e.g. for directory-side access
lists,but we can add it back if necessary. Removed for now.

  public:
   AccessVerifier() { }
   virtual ~AccessVerifier() { }
 
-  virtual bool VerifyPermissions(const std::string& client_jid,
-                                 const std::string& encoded_client_token) = 0;
+  virtual bool VerifyPermissions(const std::string& client_jid) = 0;

[Wez, 2011/11/23 01:23:04]

Do we want the |client_jid|, or the user's GAIA Id?
If this interface now controls access purely based on JID (or GAIA Id?) then
perhaps it needs a new name?

 };
 
 }  // namespace remoting
 
 #endif  // REMOTING_HOST_ACCESS_VERIFIER_H_