Added JsonMessage to the control channel.

remoting/protocol/client_stub.h

Index: remoting/protocol/client_stub.h
diff --git a/remoting/protocol/client_stub.h b/remoting/protocol/client_stub.h
index 4507ba7f821ad4dce84eef1fcd2dd50d6b76f165..e08377e47304b27357dd118b5dc5a51530b03d2e 100644
--- a/remoting/protocol/client_stub.h
+++ b/remoting/protocol/client_stub.h
@@ -18,6 +18,7 @@ namespace remoting {
 namespace protocol {
 
 class Capabilities;
+class JsonMessage;
 class PairingResponse;
 
 class ClientStub : public ClipboardStub,
@@ -32,6 +33,9 @@ class ClientStub : public ClipboardStub,
   // Passes a pairing response message to the client.
   virtual void SetPairingResponse(const PairingResponse& pairing_response) = 0;
 
+  // Send a JSON message from the host to the client.

[Wez, 2013/08/09 21:25:48]

nit: This comment is written from a host perspective, but the method name is
client-oriented.  How about SendJsonMessage / SendExtensionMessage /
SendOpaqueMessage?

[Jamie, 2013/08/09 21:39:06]

I originally had SendJsonMessage, but it quickly got confusing since both the
client and host stubs had identically-named methods. I think it's better to use
different names for the two directions. I settled on Process as a suitably vague
verb because at one end processing involves sending over the network, and at the
other it involves (or will involve, once we start making use of this feature)
checking the type field and dispatching the message.

+  virtual void ProcessHostJson(const JsonMessage& message) = 0;
+
  private:
   DISALLOW_COPY_AND_ASSIGN(ClientStub);
 };