W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > October 2019

Re: [mediacapture-record] Shouldn't remaining async methods run "in parallel"? (#131)

From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
Date: Tue, 22 Oct 2019 20:21:44 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-545136843-1571775698-sysbot+gh@w3.org>
@Pehrsons Aligning with implementations on `pause()` and `resume()` seems like a good idea.

In Chrome, pause/resume appears to [work reliably](https://jsfiddle.net/jib1/nwq5t3vr/) from `requestAnimationFrame(f)`, a useful property that would be [broken](https://jsfiddle.net/jib1/z35anrqh/) if it followed the spec (queued a task).

But for methods like `requestData`, you made a good point offline that waiting for the recording to stop "in parallel" before queuing the task might make more sense, since there might still be data in the queue to encode, and the data might have to be written to disk when writing to the blob.

GitHub Notification of comment by jan-ivar
Please view or discuss this issue at https://github.com/w3c/mediacapture-record/issues/131#issuecomment-545136843 using your GitHub account
Received on Tuesday, 22 October 2019 20:21:51 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:22:29 UTC