Rename ClientDimensions to ClientResolution and add pixel-size and DPI fields.

remoting/proto/internal.proto

 // Copyright (c) 2012 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.
 
 // Internal message types that should not be seen outside the protocol
 // directory.
 
 syntax = "proto2";
 
 import "control.proto";
 import "event.proto";
 
 option optimize_for = LITE_RUNTIME;
 
 package remoting.protocol;
 
 // Represents a message being sent on the control channel.
 message ControlMessage {
   optional ClipboardEvent clipboard_event = 1;
-  optional ClientDimensions client_dimensions = 2;
+  optional ClientResolution client_resolution = 2;

[Jamie, 2013/02/11 23:25:58]

I assume that the size difference between ClientDimensions and ClientResolution
isn't going to cause protocol incompatibilities?

[Wez, 2013/02/12 01:55:28]

These are protobufs, so you can add (and remove[*]) fields as much as you like.

[*] So long as you don't try to re-use the removed members' indices...

   optional CursorShapeInfo cursor_shape = 4;
   optional VideoControl video_control = 3;
   optional AudioControl audio_control = 5;
 }
 
 // Defines an event message on the event channel.
 message EventMessage {
   optional int64 sequence_number = 1;  // Client timestamp for event.
 
   optional KeyEvent key_event = 3;
   optional MouseEvent mouse_event = 4;
 }