The logic of how to talk to the video conferencing system doesn't need to be backed into the browser. If the API provides enough control the JS, the web app can contain the logic to talk to the video conferencing system. I know I'm going to start sounding like a broken record, but you brought up video conferencing systems as an example, so I will say it again: there are are video conferencing systems that don't use SDP for signalling. For example, there are video conferencing systems that use Jingle for signalling. Would I expect the logic of how to speak to that video conferencing system to be baked into the browser? No, I think I'd prefer it to be built into a web app built on top of a good API. Why should SDP-based video conferencing systems be treated special? On Fri, Jul 19, 2013 at 5:52 PM, Cullen Jennings <fluffy@iii.ca> wrote: > > On Jul 19, 2013, at 9:54 AM, Martin Thomson <martin.thomson@gmail.com> > wrote: > > > Negotiation is a hole. A vast, soul-sucking, waste of time. > > That's might be closer to true when you control both ends, like Skype. > > It's not true when a browser from one vendor running an application from a > scone vendor needs to talk to video conferencing system from a third vendor. > > > >
Received on Saturday, 20 July 2013 01:01:58 UTC