[Bug 17082] Discuss whether Media Source methods should be in separate object

https://www.w3.org/Bugs/Public/show_bug.cgi?id=17082

--- Comment #2 from Aaron Colwell <acolwell@chromium.org> 2012-05-21 15:26:34 UTC ---
(In reply to comment #1)
> 1. (In reply to comment #0)
> > Here are a few other follow up questions to spark discussion:
> > 1. What do we gain by moving this into a separate object?
> 
> One can have separate objects for separate streams instead of the id
> association mechanism. They can expose (or be) MediaStreams and thus integrate
> with WebRTC.

Wouldn't you still need a single object to collect all the separate objects
together into a single presentation?

Do we really want to integrate with WebRTC in this way? I always assumed that
we would do this through an HTMLMediaElement. I figured that HTMLMediaElement
would expose one or more MediaStreams and those would be connected to the
WebRTC APIs.   I figured this would be a better path because it allows us to
reuse a bunch of events, behavior, and attributes that already have well
defined meanings.

> 
> > 2. If they are placed in a separate object, can the object be associated with
> > multiple tags?
> 
> Presumably, yes. Would that be a problem?

It could make garbage collection of segments in the source buffer a little
tricky since you would have to keep track of multiple presentation time
pointers and take them into account when trying to decide what segments to
expire. I suppose this isn't too much different than the problem the HTTP cache
has to deal with, but it is extra work. 


> 
> > 3. Will this prevent declarative syntax to enable Media Source and reuse of the
> > <source> fallback mechanism?
> 
> No more than the current solution, surely? For comparison, see the
> mediagroup="" attribute on <video> which implicitly creates a MediaController
> object.

Would the onsourceopen, onsourceclose, onsourceended event handler attributes
also automatically get assigned to this object too? I'm not sure where the
right place is to draw the line for where the declarative mechanism should end
if most of the functionality is in a separate object. If we allow the
MediaSource object to get automatically created, it seems like at a minimum we
should also allow onsourceopen since that would be the easiest way to discover
this object when it gets created.

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Monday, 21 May 2012 15:27:01 UTC