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

[Tim Panton <[e-mail]>]

On 17 Oct 2011, at 08:45, Ravindran Parthasarathi wrote:

> RTCWeb server signaling plays the key role which calls for standardization as browser & RTCWebserver is not required from the same vendor.

And that is where we differ. The web server can _serve_ it's javascript to the browser. 
So the only standards needed are the pre-existing web standards of javascript and http.

The browser only has to be capable of running the javascript served to ensure compatibility.
That's the way that everything on the web works these days, from shopping carts to realtime 
chat. The browser is given site-specific code to run that interacts with site-specific code on
the web server. The web server may choose to convert those requests into a standard protocol 
for further processing (e.g. SQL), or may deal with the request internally.

Note, I'm not ruling out the use of SIP, but as  Iñaki Baz Castillo has demonstrated, that too
can be accomplished purely with existing web technologies. No embedded signalling code 
is needed.

Tim.