- From: Iñaki Baz Castillo <ibc@aliax.net>
- Date: Wed, 3 Jul 2013 02:08:33 +0200
- To: "Suhas Nandakumar (snandaku)" <snandaku@cisco.com>
- Cc: Ted Hardie <ted.ietf@gmail.com>, Christer Holmberg <christer.holmberg@ericsson.com>, cowwoc <cowwoc@bbs.darktech.org>, Robin Raymond <robin@hookflash.com>, Roman Shpount <roman@telurix.com>, Adam Bergkvist <adam.bergkvist@ericsson.com>, "piranna@gmail.com" <piranna@gmail.com>, "public-webrtc@w3.org" <public-webrtc@w3.org>, Eric Rescorla <ekr@rtfm.com>
2013/7/3 Suhas Nandakumar (snandaku) <snandaku@cisco.com>: > Instead of passing SDP between JS and WebRC stack, use a real JS > Object based API. > Instead of sending an opaque SDP blob in-the-wire send the media info > in any custom format designed by the website developer. Anyone is fine > if the receiver JS can de-serialize/decode/parse it, construct the > requires JS Object(s) with it, and pass it to the WebRTC stack via a > JS API. > >>> > just curious, how does the one define the agreed upon structure to understand the semantics of the data stored in such a data structure passed from one end-point to the another ... Imagine you design a website in which user-A must be able to send an integer, a float and a string to user-B. Of course the "signaling" would use HTTP or WebSocket. How would you do that? I can imagine 1000 ways. Why should I use a fixed blob string? -- Iñaki Baz Castillo <ibc@aliax.net>
Received on Wednesday, 3 July 2013 00:09:21 UTC