diff options
| author | hclam@chromium.org <hclam@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-05-06 21:19:29 +0000 |
|---|---|---|
| committer | hclam@chromium.org <hclam@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-05-06 21:19:29 +0000 |
| commit | c0f7082fdc8b239027b196a777180899bf7f5ce3 (patch) | |
| tree | 1b4ff8c2ca9049ef75b80f5f7c1bb7f0762de1c7 /remoting/protocol/message_decoder_unittest.cc | |
| parent | 9d85fa39bdf901eea6dc70f804e3d2a1001d07ab (diff) | |
| download | chromium_src-c0f7082fdc8b239027b196a777180899bf7f5ce3.zip chromium_src-c0f7082fdc8b239027b196a777180899bf7f5ce3.tar.gz chromium_src-c0f7082fdc8b239027b196a777180899bf7f5ce3.tar.bz2 | |
Chromoting to report roundtrip latency
Doing so by sending a sequence number, essentially the timestamp in every
envet message. Capturer at the host will pick up the latest sequence number
and pass it through the pipeline. Client will then receive it and determine
the latency.
This roundtrip latency number however doesn't include time in decoding and
rendering.
BUG=None
TEST=None
Review URL: http://codereview.chromium.org/6792038
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@84504 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'remoting/protocol/message_decoder_unittest.cc')
| -rw-r--r-- | remoting/protocol/message_decoder_unittest.cc | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/remoting/protocol/message_decoder_unittest.cc b/remoting/protocol/message_decoder_unittest.cc index 97c31ff..38526b8 100644 --- a/remoting/protocol/message_decoder_unittest.cc +++ b/remoting/protocol/message_decoder_unittest.cc @@ -34,7 +34,7 @@ static void PrepareData(uint8** buffer, int* size) { // Then append 10 update sequences to the data. for (int i = 0; i < 10; ++i) { EventMessage msg; - msg.set_timestamp(i); + msg.set_sequence_number(i); msg.mutable_key_event()->set_keycode(kTestKey + i); msg.mutable_key_event()->set_pressed((i % 2) != 0); AppendMessage(msg, &encoded_data); |