- From: Bernard Aboba via GitHub <sysbot+gh@w3.org>
- Date: Fri, 24 Jun 2022 00:02:26 +0000
- To: public-webrtc-logs@w3.org
After looking over the slides and listening to the arguments, my take is the following: 1. [The W3C design principles]([ttps://www.w3.org/TR/design-principles/#synchronous](https://www.w3.org/TR/design-principles/#synchronous)) cite interprocess communications (IPC) as a potential reason to choose async over sync, so they don't provide much in the way of definitive guidance here. 2. There is a good argument that `cropTo()` needs to be async. 3. The concerns about resource exhaustion attacks against `CropTarget()` relate more to a potential implementation issue than to the async vs. sync question. That is, resource exhaustion attacks appear addressable even if `CropTarget()` remains async. For example, resource allocation could be moved from `CropTarget()` to `cropTo()`, since the latter is async. 4. As Tim Panton pointed out, the only existing implementation uses async and the developers do not believe that a sync approach would be feasible for them. On the other hand, those who favor sync could adopt the async approach and if desired, move resource allocation and other potentially blocking operations to `cropTo()`, returning much sooner. So it would appear that all implementers should be able to "live with" async, whereas some implementers claim they cannot live with the sync approach. -- GitHub Notification of comment by aboba Please view or discuss this issue at https://github.com/w3c/mediacapture-region/issues/17#issuecomment-1165028669 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 24 June 2022 00:02:27 UTC