W3C home > Mailing lists > Public > public-media-capture@w3.org > November 2012

RE: revised recording proposal

From: Mandyam, Giridhar <mandyam@quicinc.com>
Date: Wed, 28 Nov 2012 17:55:14 +0000
To: Jim Barnett <Jim.Barnett@genesyslab.com>, Martin Thomson <martin.thomson@gmail.com>
CC: "public-media-capture@w3.org" <public-media-capture@w3.org>
Message-ID: <CAC8DBE4E9704C41BCB290C2F3CC921A16355CE3@nasanexd01h.na.qualcomm.com>
If the intention is to still be able to return valid blobs at UA-determined intervals without a timeSlice having been specified, then I don't believe recordingerror is the appropriate event to raise.  A recordingwarning would be useful in this case with an appropriate warning code, e.g. a code that would indicate "Early return of data due to memory limitations".  

-----Original Message-----
From: Jim Barnett [mailto:Jim.Barnett@genesyslab.com] 
Sent: Wednesday, November 28, 2012 9:22 AM
To: Martin Thomson; Mandyam, Giridhar
Cc: public-media-capture@w3.org
Subject: RE: revised recording proposal

In the case where the app does not specify a timeSlice (so that the UA is supposed to wait for the stream to end or for stopRecording to be called) the UA would certainly be able to return a block early by raising an error (i.e., recordingerror, followed by dataavailable, and recordingdone).  I don't think that it should be able to do this without raising an error - it's not doing what the API call asked for, and that should be an error.  "Sorry dude, I just didn't feel like it" doesn't make a great API...

- Jim

-----Original Message-----
From: Martin Thomson [mailto:martin.thomson@gmail.com]
Sent: Wednesday, November 28, 2012 12:11 PM
To: Mandyam, Giridhar
Cc: Jim Barnett; public-media-capture@w3.org
Subject: Re: revised recording proposal

On 27 November 2012 20:08, Mandyam, Giridhar <mandyam@quicinc.com> wrote:
> In other words, when the developer does not specify a timeSlice, can 
> the UA still return data at pre-set intervals?

I would hope so.  I think that a UA should be permitted to set both minimum and maximum constraints on how often it provides delineated blocks.

As an aside, I don't see any need to have the actual value being discoverable, since it is likely that the constraints on the UA will vary over time.
Received on Wednesday, 28 November 2012 17:55:43 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:26:12 UTC