Re: [rtcweb] API draft: draft-kaplan-rtcweb-api-reqs-00

Bingo... I think we want to create the conditions where a hundred different JavaScript libraries will bloom as developers try out new and innovative ways to bring real-time communications directly into the web browsers and weave it into the fabric of the web.

Yes, some (many? most?) of those libraries will suck badly ... but over time I believe the "jQuery of RTCWEB" will emerge from somewhere and suddenly people all over will be baking RTC directly into web apps using the proverbial less than 20 lines of code.

My 2 cents,
Dan

On Oct 21, 2011, at 7:24 AM, Iñaki Baz Castillo wrote:

> 2011/10/21 Christer Holmberg <christer.holmberg@ericsson.com>:
>> We need to specify what is to be used by the JS library developers. If they then design libraries that allow people to set up calls using 20 lines of code, fine, but how can WE enforce that to happen?
>> 
>> I don't think we can say that the API WE specify shall allow setting up a call using 20 lines. We can only hope (and, of course, do whatever we can do in order to allow that to happen) that the API WE specify allows someone ELSE to produce a library which then allows users to set up calls using 20 lines :)
> 
> That's exactly what I meant :)
> 
> -- 
> Iñaki Baz Castillo
> <ibc@aliax.net>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb

-- 
Dan York  dyork@lodestar2.com
http://www.danyork.com/   skype:danyork
Phone: +1-802-735-1624
Twitter - http://twitter.com/danyork
--------------------------------------------------------
All comments and opinions are entirely my own and have no connection whatsoever to any employer, past or present. Indeed, by tomorrow even I might be disavowing these comments.
--------------------------------------------------------