Re: [rtcweb] Review request for RTCWeb standard signaling protocol

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

2011/10/18 Ravindran Parthasarathi <[e-mail]>:
> Also, the attempt for "standard" signaling protocol is not an attempt to stop custom-build signaling protocol and Sec 4 of draft-partha-rtcweb-signaling-00 draft explains this as
>
> "The defining signaling protocol is not a hindrance for any innovative
>   RTCWeb signaling protocol development as it is complementary
>   solution."
>
> but standard signaling protocol facilities for the quick development of the generic RTCWeb usecase without the need of developing of new signaling protocol per website. In case you still feel that my draft does not reflect this notion, Please let me know.


When RTCweb becomes a reality there will appear thousands of
JavaScript libraries implementing different RTCweb signaling
protocols, each one with its own features and capabilities. Do you
understand that a website admin will be able to choose the one he
prefers?

Visit 100 random cool websites. Probably 50% of them use JQuery JS
library. Does it mean that each web developer had to build his own JS
library? not at all, they use JQuery.

Now your reply will be "downloading the JS library everytime is not
efficient". Ok, visit 100 random cool websites. Probably 50% of them
use JQuery JS library. How many times have you downloaded the JQuery
library (assuming that every site has its own copy of the .js)? ... 50
times. Is that a problem? not for the rest of the humans in the world.

So please stop making up issues that don't exist. The WWW world does
not work as you propose, and anyhow it has succeeded.



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