AppRTC: Use WebSockets instead of Channel API.

With this change no messages are stored on GAE. Instead, they are stored on Collider.
GAE still keeps track of which users are connected to a given room.
Note that loopback will no longer work.
But the original code is POST to GAE, not channel.send :)
What's why I think it makes sense to change to POST to GCE.

On Fri, Nov 14, 2014 at 12:30 PM, tkchin <notifications@github.com> wrote:

> In samples/web/content/apprtc/js/signaling.js:
>
> >    trace('C->S: ' + msgString);
> > -  // NOTE: AppRTCClient.java searches & parses this line; update there when
> > -  // changing here.
> > -  var path = '/message?r=' + params.roomId + '&u=' + params.clientId;
> > -  var xhr = new XMLHttpRequest();
> > -  xhr.open('POST', path, true);
> > -  xhr.send(msgString);
> > +  webSocket.send(msgString);
>
> Would rather leave the change for not waiting for channelReady when we
> move to new server logic. Was just planning to have this replace Channel
> API as a signaling channel for now.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/GoogleChrome/webrtc/pull/216/files#r20384112>.
>



-- 
-jiayl