[Chromoting] Initial plumbing for cursor shape.

remoting/client/chromoting_client.cc

Index: remoting/client/chromoting_client.cc
diff --git a/remoting/client/chromoting_client.cc b/remoting/client/chromoting_client.cc
index 4dabdd2cf30fd663e12e7901b9a1c04a7d1365f3..2d28d1df403e1104ec31b5b7aa1d6de90792e7a1 100644
--- a/remoting/client/chromoting_client.cc
+++ b/remoting/client/chromoting_client.cc
@@ -64,7 +64,7 @@ void ChromotingClient::Start(
 
   connection_->Connect(xmpp_proxy, config_.local_jid, config_.host_jid,
                        config_.host_public_key, transport_factory.Pass(),
-                       authenticator.Pass(), this, this, this, this);
+                       authenticator.Pass(), this, this, this, this, this);
 
   if (!view_->Initialize()) {
     ClientDone();
@@ -112,6 +112,13 @@ void ChromotingClient::InjectClipboardEvent(
   view_->GetClipboardStub()->InjectClipboardEvent(event);
 }
 
+void ChromotingClient::SetCursorShape(
+    const protocol::CursorShapeInfo& cursor_shape) {

[Wez, 2012/05/23 00:01:57]

Do we actually need ChromotingClient to implement CursorShapeStub?  Could we
instead pass the |view_| directly to Connect()?  (And similarly for
ClipboardStub, actually)

[garykac, 2012/05/26 01:58:01]

ChromotingClient is currently where we handle all of the messages received from
the host. We (+sergey, simon) should setup a protocol discussion meeting and
discuss how we'd like to change it.

+  if (cursor_shape.has_data()) {

[Wez, 2012/05/23 00:01:57]

The SetCursorShape() API doesn't specify any requirement that has_data() be
true, and the PepperView implementation checks it itself, so there's no need to
check here.

[garykac, 2012/05/26 01:58:01]

Done.

+    view_->SetCursorShape(cursor_shape);
+  }
+}
+
 void ChromotingClient::ProcessVideoPacket(scoped_ptr<VideoPacket> packet,
                                           const base::Closure& done) {
   DCHECK(message_loop()->BelongsToCurrentThread());