Chromoting protocol implementation based on P2P Transport API.

remoting/protocol/pepper_channel.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_PEPPER_CHANNEL_H_
+#define REMOTING_PROTOCOL_PEPPER_CHANNEL_H_
+
+#include <string>
+
+#include "base/basictypes.h"
+#include "base/threading/non_thread_safe.h"
+
+namespace pp {
+class Instance;
+}  // namespace pp
+
+namespace crypto {
+class RSAPrivateKey;
+}  // namespace crypto
+
+namespace cricket {
+class Candidate;
+}  // namespace cricket
+
+namespace remoting {
+namespace protocol {
+
+class PepperChannel : public base::NonThreadSafe {
+ public:
+  struct TransportConfig {

[Wez, 2011/09/01 01:08:29]

nit: Consider moving this out to be PepperChannelConfig?

[Sergey Ulanov, 2011/09/08 00:48:36]

Moved it of PepperChannel, but didn't rename it. It to be handy not only for
pepper channels.

+    TransportConfig();
+    ~TransportConfig();
+
+    bool nat_traversal;
+    std::string stun_server;
+    std::string relay_server;
+    std::string relay_token;
+  };
+
+  PepperChannel() { }
+  virtual ~PepperChannel() { }
+
+  virtual void Connect(const TransportConfig& config,
+                       const std::string& remote_cert) = 0;
+  virtual void AddRemoveCandidate(const cricket::Candidate& candidate) = 0;
+  virtual const std::string& name() = 0;

[Wez, 2011/09/01 01:08:29]

Some comments to explain these APIs would be handy.

[Sergey Ulanov, 2011/09/08 00:48:36]

Done.

+
+ protected:
+  DISALLOW_COPY_AND_ASSIGN(PepperChannel);
+};
+
+}  // namespace protocol
+}  // namespace remoting
+
+#endif  // REMOTING_PROTOCOL_PEPPER_CHANNEL_H_