- From: <bugzilla@jessica.w3.org>
- Date: Mon, 21 Oct 2013 06:52:50 +0000
- To: public-webrtc@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23572
Adam Bergkvist <adam.bergkvist@ericsson.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |adam.bergkvist@ericsson.com
--- Comment #1 from Adam Bergkvist <adam.bergkvist@ericsson.com> ---
(In reply to Matthew Robertson from comment #0)
> This does not match the current Chromium or Firefox implementations in which
> only single url can be specified under the "url" key:
This is a rather new feature so implementations may not have caught up yet.
> Currently in the spec there is no mention of the "url" key (only "urls") and
> there is no example that demonstrates specifying multiple urls for a single
> IceServer object. This would be a useful feature for situations in which one
> server is capable of providing several TURN protocols (TURNS, transport=tcp,
> transport=udp etc) but it is not strictly necessary, as it can currently be
> accomplished by passing in multiple IceServer objects each with a single URL.
The "url" key was replaced by "urls" which accepts both a single url string and
an array of strings. The feature is there even though the example doesn't cover
it.
> Also, there is a small typo in the example JSON at the bottom of this
> section of the spec (4.2.2.1):
>
> http://www.w3.org/TR/webrtc/#idl-def-RTCIceServer
>
> [ { urls: "stun:stun1.example.net } , { urls:"turn:turn.example.org",
> username: "user", credential:"myPassword"} ]
>
> should be (missing "):
>
> [ { urls: "stun:stun1.example.net" } , { urls:"turn:turn.example.org",
> username: "user", credential:"myPassword"} ]
Thanks for pointing this out. It will be fixed for the next release.
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
Received on Monday, 21 October 2013 06:52:52 UTC