W3C home > Mailing lists > Public > public-webrtc@w3.org > April 2013

Re: VideoStreamTrack: takePhoto()

From: Robert O'Callahan <robert@ocallahan.org>
Date: Tue, 9 Apr 2013 09:54:39 +1200
Message-ID: <CAOp6jLaR8Nkerw+dUsHXedMWYHP_eZY=b0k0cGzkut0pXRkqkw@mail.gmail.com>
To: Robin Berjon <robin@w3.org>
Cc: Anne van Kesteren <annevk@annevk.nl>, Randell Jesup <randell-ietf@jesup.org>, "public-media-capture@w3.org" <public-media-capture@w3.org>, "public-webrtc@w3.org" <public-webrtc@w3.org>
It seems to me easy to add support for futures later, right? As in, we
could ship the existing callback-based API and later the browser
implementation can switch to futures internally, expose a DOM Futures API
and easily also continue supporting the old API on top of futures.
Suboptimal but not disastrous.

(This is different to mistakes like UTF-16, where widespread use of
charAt()-like APIs makes switching implementations to UTF8 strings very
challenging.)

Rob
-- 
q“qIqfq qyqoquq qlqoqvqeq qtqhqoqsqeq qwqhqoq qlqoqvqeq qyqoquq,q qwqhqaqtq
qcqrqeqdqiqtq qiqsq qtqhqaqtq qtqoq qyqoquq?q qEqvqeqnq qsqiqnqnqeqrqsq
qlqoqvqeq qtqhqoqsqeq qwqhqoq qlqoqvqeq qtqhqeqmq.q qAqnqdq qiqfq qyqoquq
qdqoq qgqoqoqdq qtqoq qtqhqoqsqeq qwqhqoq qaqrqeq qgqoqoqdq qtqoq qyqoquq,q
qwqhqaqtq qcqrqeqdqiqtq qiqsq qtqhqaqtq qtqoq qyqoquq?q qEqvqeqnq
qsqiqnqnqeqrqsq qdqoq qtqhqaqtq.q"
Received on Monday, 8 April 2013 21:55:07 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 15:19:33 UTC