W3C home > Mailing lists > Public > public-html-media@w3.org > June 2012

: [MSE] Moving Media Source methods into a separate object.

From: Sunyang (Eric) <eric.sun@huawei.com>
Date: Sun, 17 Jun 2012 08:17:27 +0000
To: David Dorwin <ddorwin@google.com>, Aaron Colwell <acolwell@google.com>
CC: "public-html-media@w3.org" <public-html-media@w3.org>
Message-ID: <9254B5E6361B1648AFC00BA447E6E8C32AEA916E@szxeml545-mbx.china.huawei.com>
What kind of URL returned by getURL?
createObjectURL can return a relative short URL which will reduce  the web page size, like below

Does getURL will return the same kind URL? If getURl return URL using similar like readAsDataURL,it will add more size to the web page.

Whats more it seems from specification, MediaSource is a part of Media Element, and we have mediaSourceurl attribute in speci.
So why we need another getURL method?

If using MediaSource, do you mean, MediaSource is separate with media element, that we can not use MediaSourceUrl attribute?

: David Dorwin [mailto:ddorwin@google.com]
ʱ: 2012617 11:08
ռ: Aaron Colwell
: public-html-media@w3.org
: Re: [MSE] Moving Media Source methods into a separate object.

Associating the MediaSource with a <video> would be similar to LocalMediaStream.
1. Create a MediaSource object.
2. Use createObjectURL() to get a blob URL for the MediaSource object.

Does this imply overloading createObjectURL() to accept a MediaSource object?
A new URL is created every time createObjectURL() is called, so one might have multiple URLs pointing to the same MediaSource object. Does this pose any problems?
Does it make sense to just add getURL() to MediaSource instead?

3. Assign the blob URL to HTMLMediaElement.src.

What happens if the URL is associated with multiple HTMLMediaElements? Sharing data might be nice, but what are the implications for implementations?
Received on Sunday, 17 June 2012 08:20:25 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 15:48:22 UTC