- From: Martin Thomson <martin.thomson@gmail.com>
- Date: Fri, 13 Jun 2014 09:49:51 -0700
- To: tim panton <thp@westhawk.co.uk>
- Cc: "Makaraju, Maridi Raju (Raju)" <Raju.Makaraju@alcatel-lucent.com>, "kiran.guduru@samsung.com" <kiran.guduru@samsung.com>, Adam Bergkvist <adam.bergkvist@ericsson.com>, "Stefan H?kansson LK" <stefan.lk.hakansson@ericsson.com>, Harald Alvestrand <harald@alvestrand.no>, Justin Uberti <juberti@google.com>, "public-webrtc@w3.org" <public-webrtc@w3.org>
On 13 June 2014 06:30, tim panton <thp@westhawk.co.uk> wrote: > Why not use a javascript interval ? http://www.w3schools.com/jsref/met_win_setinterval.asp > > This continuous, needless adding of special case telephony centric APIs is exactly what is holding webRTC back. > Web developers now think that it is only for implementing clones of a telephone, so it isn’t for them. I agree. The basic timing functions are fine, because they let you get tones on the wire quickly and easily. Anything more complex than that and I think we can let someone build a more fully featured wrapper API.
Received on Friday, 13 June 2014 16:50:19 UTC