Chromoting to report roundtrip latency

remoting/proto/video.proto

Index: remoting/proto/video.proto
diff --git a/remoting/proto/video.proto b/remoting/proto/video.proto
index b9bd53c784ee8ef88ca24be64ce329c40d10d6d0..97cf36ae8c32d6de4c9910c95dff442deff415a7 100644
--- a/remoting/proto/video.proto
+++ b/remoting/proto/video.proto
@@ -1,4 +1,4 @@
-// Copyright (c) 2010 The Chromium Authors. All rights reserved.
+// 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.
 
@@ -91,4 +91,8 @@ message VideoPacket {
 
   // Time in milliseconds spent in encoding this video frame.
   optional int32 encode_time_ms = 8;
+
+  // A sequence number is provided by client used to measure round trip
+  // latency.
+  optional int64 client_sequence_number = 9;

[Wez, 2011/04/05 13:46:20]

This comment suggests that the Host could use the client_sequence_number for
timings itself - as we've discussed previously, it's better not to do so. 
Really the client_sequence_number is a Host-opaque sequence number supplied in
the most recent input event the Host received from the Client, right?

[Alpha Left Google, 2011/04/08 00:07:20]

Done.

 }