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

remoting/proto/control.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.
 //
 // Protocol for control messages.
 
 syntax = "proto2";
 
 option optimize_for = LITE_RUNTIME;
 
 package remoting.protocol;
 
-message ClientDimensions {
-  // Width and height of the client.
-  optional int32 width = 1;
-  optional int32 height = 2;
+message ClientResolution {
+  // Legacy width and height of the client in Density-Independent Pixels
+  optional int32 dips_width = 1;
+  optional int32 dips_height = 2;

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

I assume the names are only important for the accessor functions? In other
words, this doesn't break protocol compatibility?

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

The numbers identify the fields at the protocol level - you can rename stuff
e.g. field to obsolete_field so long as the numbers are unmodified.

+
+  // Width and height of the client in device pixels.
+  optional int32 width = 3;
+  optional int32 height = 4;
+
+  // Horizontal and vertical DPI of the screen. If either of these is zero or
+  // unset, the corresponding DPI should be assumed to be 96 (Windows' default)
+  optional int32 x_dpi = 5;
+  optional int32 y_dpi = 6;
 }
 
 message VideoControl {
   // Enables the video channel if true, pauses if false.
   optional bool enable = 1;
 }
 
 message AudioControl {
   // Enables the audio channel if true, pauses if false.
   optional bool enable = 1;
 }
 
 message CursorShapeInfo {
   // Width, height (in screen pixels) of the cursor.
   optional int32 width = 1;
   optional int32 height = 2;
 
   // X,Y coordinates (relative to upper-left corner) of the cursor hotspot.
   optional int32 hotspot_x = 3;
   optional int32 hotspot_y = 4;
 
   // Cursor pixmap data in 32-bit BGRA format.
   optional bytes data = 5;
 }