W3C home > Mailing lists > Public > public-sysapps@w3.org > October 2012

Re: Telephony API draft

From: Poussa, Sakari <sakari.poussa@intel.com>
Date: Tue, 23 Oct 2012 07:13:29 +0000
To: Jonas Sicking <jonas@sicking.cc>, "Kis, Zoltan" <zoltan.kis@intel.com>
CC: EDUARDO FULLEA CARRERA <efc@tid.es>, "public-sysapps@w3.org" <public-sysapps@w3.org>, JOSE MANUEL CANTERA FONSECA <jmcf@tid.es>
Message-ID: <CCAC1DE5.217B7%sakari.poussa@intel.com>
On 10/22/12 12:45 PM, "Jonas Sicking" <jonas@sicking.cc> wrote:

>On Sat, Oct 20, 2012 at 2:31 PM, Kis, Zoltan <zoltan.kis@intel.com> wrote:
>> Do you think we should take out for now the recording feature? It could
>> seen as a convenience function for the developers. My thinking was that
>> Telephony API should facades most means to dialer developers supporting
>> typical dialer UI designs, and the binding implementations would
>>connect the
>> dots.
>The API as it's currently defined isn't enough to implement a
>recording feature. There's no way to actually access the recorded
>calls and play them to the user, and there's no way to specify the
>file format parameters to be used to record the call.
>So I definitely think that we need to change the API from it's current

I agree. That is, I don't see the need for the record functionality in
this API. Or in any API for this purpose.

BR; Sakari
Received on Tuesday, 23 October 2012 07:14:04 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:36:10 UTC