search

webRTC-io / webRTC.io

An abstraction layer for webRTC. Aim is to simplify the HTML5 web standard webRTC in a similar manner to socket.io w/ websockets. Highly experimental technology
1.6k stars 293 forks source link

add an additional transport layer #6

Open benbrittain opened 11 years ago

benbrittain commented 11 years ago

possibly XMLHttpRequest? In the future we are going to want webRTC as a transport layer, but we need a data channel first.

auchenberg commented 11 years ago

Why not just use socket.io as the transport-layer abstraction?

VGubarev commented 11 years ago

Because if your browser supports WebRTC, it just supports WebSocket. And WS it's better data- chanel than long pooling, ajax etc.

auchenberg commented 11 years ago

I agree that WS is a better data-channel, but the reality is that most server-setup's don't allow WS due to firewall and loadbalancer issues. This is the main reason why I see a need to an alternative transport method for the data-channel. For example isn't not possible to deploy WebRTC.io on PAAS platforms like Heroku, AppFog, Nodester, etc, because they don't support WS (yet).

Socket.io would be a drop-in replacement for the WS-server, since it can be used as a cross-browser WS implementation.

The WebRTC P2P connection between is a different thing, since the environment is much different, and is adapting faster, then the traditional server-setups.