W3C home > Mailing lists > Public > public-media-capture@w3.org > August 2015

Use of BlobEvent in MediaStream Recorder and ImageCapture

From: Mandyam, Giridhar <mandyam@qti.qualcomm.com>
Date: Mon, 31 Aug 2015 22:04:29 +0000
To: "public-media-capture@w3.org" <public-media-capture@w3.org>
Message-ID: <dafcd550dea6424bb78f3da02da300b9@NASANEXM01C.na.qualcomm.com>
Hi All,
Seeking advice on the attached issue posted in GH.

BlobEvent was defined as a convenience wrapper for an associated event handler, but what was being returned was nothing but a Blob (see ImageCapture spec http://www.w3.org/TR/image-capture/#blobevent).  Now ImageCapture is a fully promise-based API.  I don’t think there is a need for defining custom events in the ImageCapture spec anymore.  Am I correct in my understanding?

I also don’t think the same reasoning holds for Recording though, and the event wrapper for Blob is still required.  Maybe recording should also become a Promise-based API, but that is a different debate.

Also, specific request to all – please file ImageCapture issues against ImageCapture’s GH repo (https://github.com/w3c/mediacapture-image).  It helps in tracking.

-Giri Mandyam, MediaStream ImageCapture editor

From: Miguel Casas-Sanchez [mailto:notifications@github.com]
Sent: Monday, August 31, 2015 2:46 PM
To: w3c/mediacapture-record
Subject: [mediacapture-record] BlobEvent is defined in both MediaStream Recorder and MediaStream ImageCapture, consider factoring them out (#16)


In [1] and [2], respectively.

[1] http://www.w3.org/TR/mediastream-recording/#blob-event

[2] http://www.w3.org/TR/image-capture/#blobevent


—
Reply to this email directly or view it on GitHub<https://github.com/w3c/mediacapture-record/issues/16>.
Received on Monday, 31 August 2015 22:05:03 UTC

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