- From: Bernard Aboba via GitHub <sysbot+gh@w3.org>
- Date: Wed, 31 May 2017 16:25:41 +0000
- To: public-webrtc@w3.org
aboba has just created a new issue for https://github.com/w3c/webrtc-pc: == Inconsistencies in Asynchronous Task Queueing == >From EKR: https://lists.w3.org/Archives/Public/public-webrtc/2017May/0166.html I have not studied all the algorithms for how to handle asynchronous task queuing, but we seem kind of inconsistent on exactly when: - We report errors synchronously - When the task becomes due, if conditions X apply, don't run it - When the task comes due, run the algorithm and then check to see if condition X applies and then don't report. More generally, there is an enormous amount of boilerplate for handling deferred operations of various kinds. It would be far better if there were a single generic algorithm for handling all the deferred/queued operations and then we just defined the inner loop of those. Generally, I tend to think that more things should be async... That would make reasoning about this a lot easier. Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1271 using your GitHub account
Received on Wednesday, 31 May 2017 16:25:47 UTC