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

RE: recording

From: Sunyang (Eric) <eric.sun@huawei.com>
Date: Tue, 20 Nov 2012 01:44:30 +0000
To: Adam Bergkvist <adam.bergkvist@ericsson.com>
CC: Jim Barnett <Jim.Barnett@genesyslab.com>, "public-media-capture@w3.org" <public-media-capture@w3.org>
Message-ID: <9254B5E6361B1648AFC00BA447E6E8C32AED849B@szxeml545-mbx.china.huawei.com>

> -----Original Message-----
> From: Adam Bergkvist [mailto:adam.bergkvist@ericsson.com]
> Sent: Monday, November 19, 2012 7:02 PM
> To: Sunyang (Eric)
> Cc: Jim Barnett; public-media-capture@w3.org
> Subject: Re: recording
> 
> On 2012-11-16 10:20, Sunyang (Eric) wrote:
> >
> >> -----Original Message-----
> >> From: Adam Bergkvist [mailto:adam.bergkvist@ericsson.com]
> >> Sent: Tuesday, November 13, 2012 8:32 PM
> >> To: Jim Barnett
> >> Cc: public-media-capture@w3.org
> >> Subject: Re: recording
> >>
> [...]
> >> I liked the old requestData() rather than getData(). If a method is
> >> prefixed "get" it's tempting to read a return value.
> >>
> >
> > Any difference? getData can return a BLOB object, requestData also do the
> same thing.
> 
> getData() can't return a Blob since the operations involved in preparing
> the return value could be time consuming and block the event loop too
> long. getData()/requestData() is more a request to fire the
> "dataavailable" event with new data as soon as possible. That's why I
> like the requestData() name better.
> 

Got it, requestData will not cause fire event immediately, but getData() need immediate return value.
Now I am in favor of requestData.

> /Adam




Yang
Huawei
Received on Tuesday, 20 November 2012 01:45:13 UTC

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