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

Re: Teleco Integrators vs Web Developers vs Browser Implementers

From: Roman Shpount <roman@telurix.com>
Date: Fri, 28 Jun 2013 19:52:56 -0400
Message-ID: <CAD5OKxsTMqja8t3W9wka-zhP78Xgei32ytuDcMRbB3OVV=jsmQ@mail.gmail.com>
To: "piranna@gmail.com" <piranna@gmail.com>
Cc: Ted Hardie <ted.ietf@gmail.com>, Adam Bergkvist <adam.bergkvist@ericsson.com>, Gili <cowwoc@bbs.darktech.org>, public-webrtc <public-webrtc@w3.org>
I was talking about addICECandidate method for setting ICE candidates
(remote addresses) and draft-ivov-rtcweb-noplan-01 proposal to manage media
streams.
_____________
Roman Shpount


On Fri, Jun 28, 2013 at 7:32 PM, piranna@gmail.com <piranna@gmail.com>wrote:

> > We are
> > already (or at least seriously considering) setting communication
> addresses
> > and media lines via JavaScript API calls.
>
> Where can I be able to read about this? "Communication addresses" is
> expected to identify and look-up other peers, for example using an
> UUID? I'm fairly interested on this point, since it's what I'm
> currently investigating and doing myself
> (http://github.com/ShareIt-project/WebP2P.io) and would be great if
> it's defined a more standard solution for this issue... :-)
>
>
> --
> "Si quieres viajar alrededor del mundo y ser invitado a hablar en un
> monton de sitios diferentes, simplemente escribe un sistema operativo
> Unix."
>  Linus Tordvals, creador del sistema operativo Linux
>
Received on Friday, 28 June 2013 23:53:25 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 15:19:34 UTC