- From: Jim Barnett <Jim.Barnett@genesyslab.com>
- Date: Wed, 2 Jan 2013 15:30:40 +0000
- To: Adam Bergkvist <adam.bergkvist@ericsson.com>
- CC: "public-media-capture@w3.org" <public-media-capture@w3.org>
Adam, Yes, I used Event and CustomEvent in an earlier draft, but I was told it would be better to use more specific event types. - Jim -----Original Message----- From: Adam Bergkvist [mailto:adam.bergkvist@ericsson.com] Sent: Wednesday, January 02, 2013 8:29 AM To: Jim Barnett Cc: public-media-capture@w3.org Subject: Re: event definitions On 2013-01-02 10:52, Adam Bergkvist wrote: > On 2012-12-20 16:48, Jim Barnett wrote: >> I'm trying to clean up the event definitions in the recording draft >> and notice the following: >> >> 1.MediaStreamEvent is defined in the webRTC spec (section 8.5). >> Shouldn't that be moved to the gUM spec since that's where >> MediaStream is defined? >> >> 2.The gUM spec mentions MediaStreamTrackEvent, but doesn't define it. >> >> Both these event types can be used in the recording spec, so I'd like >> to link to their definitions elsewhere, rather than copying and >> risking getting out of synch. >> > > I think we could move the MediaStreamTrackEvent definition to the > Media Capture spec and add text that says that this event is used when > a MediaStream is updated by the platform (i.e. not directly with > addTrack()/removeTrack()). > > I'm not sure about MediaStreamEvent. It's used to deliver a new remote > stream and not as tightly coupled to the internals of the MediaStream > API as MediaStreamTrackEvent is. > > I remember that an old version of the recording API used > MediaStreamEvent, but I don't see it in the latest version. But then I didn't look at the latest version either. :) I see now that "recording", "stoprecording" and other events use MediaStreamEvent. I think we could go with a simple Event here since the stream is accessible via the event anyhow (evt.target.mediaStream). /Adam
Received on Wednesday, 2 January 2013 15:31:06 UTC