W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > June 2017

[webrtc-pc] Enqueue an operation vs queue a task

From: Soares Chen via GitHub <sysbot+gh@w3.org>
Date: Tue, 06 Jun 2017 08:24:16 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issues.opened-233814797-1496737455-sysbot+gh@w3.org>
soareschen has just created a new issue for https://github.com/w3c/webrtc-pc:

== Enqueue an operation vs queue a task ==
Section 3 imports the concept of queue a task from HTML5.

Section defines _"Enqueue an operation"_ which has an operation queue of running one task at a time.

I tried searching through the spec and there are two phrases being used:

1. queue a task that runs the following steps
2. enqueue the following steps

I'd guess that (1) refers to the HTML5 task and (2) refers to the operation queue. If so, the only section that make use of enqueue operation is _"Set the RTCSessionSessionDescription"_.

If that is correct, I think the sections should be better organized to document the use. In particular, place the _"Enqueue an operation"_ side by side with _"Set the RTCSessionSessionDescription"_, and add a note to clarify that the remaining sections refer to the HTML5 task.

Because _"Enqueue an operation"_ is introduced so early and prominently in the spec, I have been wrongly assuming that all tasks are enqueued as operation instead of HTML5 task. :(

Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1347 using your GitHub account
Received on Tuesday, 6 June 2017 08:24:22 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:21:39 UTC