- From: <piranna@gmail.com>
- Date: Sat, 6 Jul 2013 01:23:53 +0200
- To: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
- Cc: Eric Rescorla <ekr@rtfm.com>, Tim Panton <thp@westhawk.co.uk>, Robin Raymond <robin@hookflash.com>, cowwoc <cowwoc@bbs.darktech.org>, "public-webrtc_w3.org" <public-webrtc@w3.org>, Roman Shpount <roman@telurix.com>, Christer Holmberg <christer.holmberg@ericsson.com>, Adam Bergkvist <adam.bergkvist@ericsson.com>, Iñaki Baz Castillo <ibc@aliax.net>, Ted Hardie <ted.ietf@gmail.com>, Parthasarathi R <partha@parthasarathi.co.in>, Martin Thomson <martin.thomson@gmail.com>, Martin Steinmann <martin@ezuce.com>
> Should the SDP on the wire be limited to support what legacy devices > support? > > Then we could add an independent API to tell the browser what data to put > into the srtp stream when it's talking to non-legacy devices. This would be > just an API that is used between the JS dev and the browser to determine the > capabilities of the device and manipulate what goes into the srtp stream. > > Just a thought... > Very clever solution, this will warrant that if it can be done just with "basic" configuration it would work with current, legacy devices, and if you need to use the API then it would only work with "advanced" ones (browsers, or anything developed from now). I like it. -- "Si quieres viajar alrededor del mundo y ser invitado a hablar en un monton de sitios diferentes, simplemente escribe un sistema operativo Unix." – Linus Tordvals, creador del sistema operativo Linux
Received on Friday, 5 July 2013 23:24:41 UTC