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

[Iñaki Baz Castillo <[e-mail]>]

2011/10/21 Hadriel Kaplan <[e-mail]>:
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>
>        Title           : API Requirements for RTCWEB-enabled Browsers
>        Author(s)       : Hadriel Kaplan
>                         Dan Burnett
>                         Neil Stratford
>                         Tim Panton
>        Filename        : draft-kaplan-rtcweb-api-reqs-00.txt
>        Pages           : 13
>        Date            : 2011-10-21
>
>  This document discusses the advantages and disadvantages of several
>  proposed approaches to what type of API and architectural model
>  RTCWeb Browsers should expose and use.  The document then defines
>  the requirements for an API that treats the Browser as a library and
>  interface as opposed to a self-contained application agent.
>
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-kaplan-rtcweb-api-reqs-00.txt


I love this draft.

Just a comment. The draft says:

---------------------
   There has been discussion that RTCWeb should strive to enable media
   communication session with about "20 lines of code".  We assert the
   only means of achieving that goal in a production-deployment manner
   is to use Javascript, and in particular Javascript libraries.
---------------------

I would like to insist on that. When people says "20 lines of code" I
expect that they mean the number of lines that a *high-user* needs to
write in order to code a RTC session. But I assume that such
*high-user* is using a JS library the browser retrieved from the
website, and that JS library deals with all the complexity at low
level.

So for example, let's take a look to Phono JS library. It does allow
implementing a call in 20 lines of code, but the library itself has
more than 20 lines :)
Anyhow the high-user must only deal with Phono JS API and using such
API can code a call in 20 lines.

That's the point IMHO. Let's the complexity to the developers of JS
libraries, and they will make a simple API for end users. This is how
WWW works and IMHO RTCweb should go in the same direction. We cannot
and must no change WWW.

Best regards.


-- 
Iñaki Baz Castillo
<[e-mail]>