summaryrefslogtreecommitdiffstats
path: root/wsd/protocol.txt
diff options
context:
space:
mode:
authorTor Lillqvist <tml@collabora.com>2021-07-21 12:34:48 +0300
committerTor Lillqvist <tml@collabora.com>2021-07-21 13:26:23 +0300
commit522431a82e245f93852c9888953cbd3a6a4cae49 (patch)
treecbf3cc9967a72ad549f94135a06092357c42fd49 /wsd/protocol.txt
parentCheck directly that the result is exactly what we expect (diff)
downloadonline-522431a82e245f93852c9888953cbd3a6a4cae49.tar.gz
online-522431a82e245f93852c9888953cbd3a6a4cae49.zip
We generate 'S' and 'F' "Async" Trace Events in loleaflet, not 'b' and 'e'
"Async" here refers a specific kind of data in the Trace Event JSON format, not asynchrony in general. Actually, we don't have code that would generate such yet in loleaflet. Just the createAsyncTraceEvent function in Socket.js. Quite possibly the "Complete" events (a.k.a. ProfileZones) are all we need. Signed-off-by: Tor Lillqvist <tml@collabora.com> Change-Id: I611ccd4b964bcacdd1050893f70dbdb813ee3c34
Diffstat (limited to 'wsd/protocol.txt')
-rw-r--r--wsd/protocol.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/wsd/protocol.txt b/wsd/protocol.txt
index 42bbd9ece8..060efc9d75 100644
--- a/wsd/protocol.txt
+++ b/wsd/protocol.txt
@@ -70,9 +70,9 @@ TRACEEVENT name=<name> ph=<letter> ts=<timestamp> <more parameters>... [ args=<J
'i': An "Instant" event.
- 'b', 'e': The begin and end of an "Async" event. In addition to
+ 'S', 'F': The start and finish of an "Async" event. In addition to
the name, the messages have an "id" parameter, a unique number
- that must be the same for the 'b' and 'e' messages.
+ that must be the same for the 'S' and 'F' messages.
'X': A "complete" event. The "dur" parameter is the duration
between the beginning of the thing being timed and the time when