summaryrefslogtreecommitdiffstats
path: root/remoting/DEPS
diff options
context:
space:
mode:
authorhclam@chromium.org <hclam@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2011-05-06 21:19:29 +0000
committerhclam@chromium.org <hclam@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2011-05-06 21:19:29 +0000
commitc0f7082fdc8b239027b196a777180899bf7f5ce3 (patch)
tree1b4ff8c2ca9049ef75b80f5f7c1bb7f0762de1c7 /remoting/DEPS
parent9d85fa39bdf901eea6dc70f804e3d2a1001d07ab (diff)
downloadchromium_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/DEPS')
0 files changed, 0 insertions, 0 deletions