W3C home > Mailing lists > Public > public-webrtc@w3.org > July 2013

Re: Expose capabilities / Allow for IP:Post based connections / Better abstraction

From: <piranna@gmail.com>
Date: Mon, 8 Jul 2013 12:31:10 +0200
Message-ID: <CAKfGGh1SQ4zSX46OmCOTnJcaNu4bYdTsptSYs2-Ck7Jc2quJyw@mail.gmail.com>
To: Adam Bergkvist <adam.bergkvist@ericsson.com>
Cc: Johannes Hange <moooitic@mailbox.tu-berlin.de>, public-webrtc <public-webrtc@w3.org>
> I assume that your polyfill uses WebSocket as the transport?

Yes, my polifill
(https://github.com/ShareIt-project/DataChannel-polyfill) is using
WebSockets as underlying data transport (UDT on the WebRTC

> In that case
> you connect the two peers via a server (and not peer-to-peer); hence no need
> to exchange candidates. The majority of the code (and the complicated parts)
> in the DataChannel example (in the spec), is actually connecting the two
> peers. Once you have that, creating a DataChannel is rather easy.
So candidates are mandatory? What's the data that needs to be
interchanged? I have seen that up to seven candidates are
interchanged, why so much? Couldn't this be made transparent to the

> The web app can't set it's own ports and the receiver ip/ports for security
> reasons.

I totally agree, publicly allow random connection with IP:port is a
security issue, but there should be an option to directly connect
without needing a handshake server and having at most the STUN data.
At this moment I'm using UUIDs to identify the peers on the server and
interchange the SDP strings, but there should be an easier,
no-server-dependent solution to be able to develop a real serverless
P2P architecture...

> Compare WebSockets [1], which similarly to WebRTC is exposed in
> regular browsers, to the Raw Socket API [2] that developed in SysApps which
> is targeting packaged applications and other cases where you have a manifest
> and the app runs in an elevated security mode.
> /Adam
> [1] http://dev.w3.org/html5/websockets/
> [2] http://www.w3.org/2012/sysapps/raw-sockets/
Oh, well... good to know about raw-sockets, but seems really crazy as
a solution... Isn't there any solution half-way from raw-sockets to
websockets/datachannels, or couldn't be able to be developed?

"Si quieres viajar alrededor del mundo y ser invitado a hablar en un
monton de sitios diferentes, simplemente escribe un sistema operativo
 Linus Tordvals, creador del sistema operativo Linux
Received on Monday, 8 July 2013 10:32:02 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:17:49 UTC