On Fri, Jun 17, 2016 at 6:43 PM, Jan-Ivar Bruaroey <j...@mozilla.com> wrote:
> Data channels are modeled on web sockets, and I see we do this for web > sockets. https://bugzil.la/692067 > > However, data channels are typically opened to other *clients*, not > servers. > While WebRTC is typically used to connect between clients, this is by no means necessary. My understanding is that anyone can set up a server that accepts WebRTC data channel connections. > > What would the ContentLocation URI be in this case? The (dynamic) IP used > to reach the other client? > I think it would IP addresses be in most cases, unless ice candidates can be urls too. > > This seems easily circumvented by routing data through another client that > doesn't use content policy. In the advertising example, this means an advertiser would have to push this new IP to ALL publishers on their platform. In the example I proposed, the advantage to publishers is that they only need to paste in a snippet of javascript with hard coded ICE candidates. This means they don't require anything sophisticated on the backend to serve ads. Using dynamic IPs means that publishers would need to A) regularly paste in a new version of the advertising code or B) set up a backend to fetch those IPs regularly and update the hard coded values. Either of those are much more complicated for the publisher when compared to just pasting in javascript. _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
