W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > May 2022

Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17)

From: Elad Alon via GitHub <sysbot+gh@w3.org>
Date: Mon, 23 May 2022 16:31:48 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-1134892183-1653323505-sysbot+gh@w3.org>
> @eladalon1983 I'm sorry are you still arguing for setTimeout? Do you understand its purpose is specifically to induce delay? If you meant to simply not wait for completion, just remove the await instead (but let's move this idea to https://github.com/w3c/mediacapture-region/issues/19):

Messages only make sense in their proper context.
* **What I did:** I described a technique by which a synchronous function could participate in cropping, even if the developer did not wish to make that function asynchronous.
* **What I did NOT do:** Advocate for using setTimeout() in the general case of cropping.

> Back to performance. I've shown a sync minting API in JS is [actually faster](https://github.com/w3c/mediacapture-region/issues/17#issuecomment-1132232768) because otherwise [you're essentially serializing the two steps of generating the key and postMessaging it](https://github.com/w3c/mediacapture-region/issues/17#issuecomment-1130846621). This seems to undermine your hypothesis that your design is faster. Do you disagree?

Did you read [my response](https://github.com/w3c/mediacapture-region/issues/17#issuecomment-1132272361)?

-- 
GitHub Notification of comment by eladalon1983
Please view or discuss this issue at https://github.com/w3c/mediacapture-region/issues/17#issuecomment-1134892183 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 23 May 2022 16:31:49 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 6 May 2023 21:19:57 UTC