Adjust telemetry to DevTools protocol changes
commitd7bd0e93027a8f0e4291d3d4d304192465e19ad3
authorcaseq@chromium.org <caseq@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>
Wed, 24 Jul 2013 15:34:15 +0000 (24 15:34 +0000)
committercaseq@chromium.org <caseq@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>
Wed, 24 Jul 2013 15:34:15 +0000 (24 15:34 +0000)
treedaea7c515bedfe01b4d9582378efea711796ec7b
parent08b9203f3b081b09df3015695833b5550ab67c74
Adjust telemetry to DevTools protocol changes

We used to send trace events as stringized JSON within DevTools
protocol messages. We're changing them to be sent as raw objects,
sort of first-class DevTools protocol payload, which removes
the need for extra level of json de-serialization.
This adopts telemetry so it digest both old and new formats.

See also: https://codereview.chromium.org/18474006/

BUG=

Review URL: https://chromiumcodereview.appspot.com/19617003

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@213433 0039d316-1c4b-4281-b951-d872f2087c98
tools/telemetry/telemetry/core/chrome/tracing_backend.py
tools/telemetry/telemetry/core/chrome/tracing_backend_unittest.py