Re: Call for Consensus (CfC) on Issue 17 of "Region Capture"

I should perhaps amplify my reasoning (since everyone else is)
The presumption of an async API is that it is (relatively) expensive and time to completion is unknown.
Developers will avoid _speculatively_ creating crop targets if they think they are expensive. They definitely won’t create _multiple_
croptargets if the API is async (unless they are _certain_ they will be used).

I’d rather have a situation where a page creates multiple crop targets (i.e. one which crops subtitles and one that does not.)

At in any given capture only one of these targets will be used - which (presumably) is counter to chrome’s current implementation which 
seems to allocate a real resource of some sort when ever a region is tagged as a _potential_ source of cropping.

The other area is failure modes - Google’s design gives us 2 places a cropTarget can fail - once when it is minted and once when it is used.
The fallback strategies in the 2 apps are different and _can’t_ easily be co-ordinated. 
If cropTarget is sync and produces a token, then it pretty much can’t fail - meaning that all the error handling is in the right place - in the capturing app.

Tim.

> On 12 Jul 2022, at 11:59, T H Panton <tim@pi.pe> wrote:
> 
> In my opinion 
> 
> CropTarget production should * be synchronous
> 
> * that’s an rfc2119 style use of ‘should'
> 
> T.
> 
>> On 12. Jul 2022, at 09:34, Bernard Aboba <Bernard.Aboba@microsoft.com> wrote:
>> 
>> This is a Call for Consensus (CfC) on Issue 17 of "Region Capture". 
>> 
>> Section 6.2 of the "Region Capture" specification contains a Note: 
>> 
>> 
>> 
>> Issue 17 of "Region Capture" is available here: 
>> What makes CropTarget special to require an asynchronous creation? · Issue #17 · w3c/mediacapture-region · GitHub
>> 
>> The Discussion of Issue 17 at the June 23 Virtual Interim is available here: 
>> WEBRTCWG-2022-06-23 - Google Slides
>> 
>> Minutes of the June 23 Virtual Interim are here: 
>> https://www.w3.org/2022/06/23-webrtc-minutes.html 
>> 
>> In replying to this CfC, respondents should indicate one of the following:
>> 
>> * CropTarget production should be synchronous.
>> * CropTarget production should be asynchronous.
>> 
>> The CfC will last until July 26, 2022 at midnight Pacific Time. 
>> 
>> Bernard
>> For the Chairs
> 
>

Received on Wednesday, 27 July 2022 09:44:15 UTC