- From: Jonas Sicking <jonas@sicking.cc>
- Date: Fri, 19 Oct 2012 16:50:16 -0700
- To: EDUARDO FULLEA CARRERA <efc@tid.es>
- Cc: "public-sysapps@w3.org" <public-sysapps@w3.org>, JOSE MANUEL CANTERA FONSECA <jmcf@tid.es>, "Kis, Zoltan (zoltan.kis@intel.com)" <zoltan.kis@intel.com>
On Fri, Oct 19, 2012 at 3:50 AM, EDUARDO FULLEA CARRERA <efc@tid.es> wrote: > Hi all, > > I have uploaded an initial draft of the Telephony API [1], which has been jointly prepared by Zoltan Kis, Jose M. Cantera and myself, who are willing to act as co-editors of this spec. > > This draft is based to a great extent on the Firefox OS (B2G) WebTelephony API, but also incorporates additional feedback received mainly from Zoltan. Note that this draft has been edited using ReSpec, but we can migrate it later on to Anolis if necessary. > > Looking forward to your feedback. I don't really understand the "record" feature. Is the intent that the device will be doing the recording? I.e. could exactly the same thing be accomplished if we permitted access to the audio stream and then allowed the webpage to store the data as it saw fit (for example using IndexedDB). Or is the intent that the network somehow does the recording and so the implementation of the record feature will somehow communicate with the network? If the former, is recording really a commonly enough used feature that we should add it to the spec? Where is the recoding saved to? Don't we need to add parameters to control things like file name, file format, encoding and encoding parameters? Wouldn't it be better to support getting access to the audio stream if this is really important since that would allow additional usecases. Or at least wait with supporting this usecase until we have audio stream access. I've never seen a device which supports recording but maybe this is popular in markets that I'm not part of? Such as enterprise or other countries? / Jonas
Received on Friday, 19 October 2012 23:51:14 UTC