W3C home > Mailing lists > Public > public-webrtc@w3.org > October 2011

Re: Non-browser interop

From: Harald Alvestrand <harald@alvestrand.no>
Date: Wed, 12 Oct 2011 18:14:52 +0200
Message-ID: <4E95BCFC.2060402@alvestrand.no>
To: Shaun Crampton <Shaun.Crampton@metaswitch.com>
CC: "public-webrtc@w3.org" <public-webrtc@w3.org>
On 10/12/11 02:17, Shaun Crampton wrote:
> Hi,
>
> Iíve been experimenting with non-browser webRTC interop (trying to get 
> a PeerConnection-using browser to talk to some other device via my 
> server) using Ericsson's demo browser.  The biggest hurdle Iíve hit so 
> far is that there doesnít seem to be any way to turn off negotiation 
> of the ďtextĒ channel, which occurs before negotiation of the 
> audio/video channel that Iím expecting.  I guess I can negotiate a 
> black hole address for the text or similar but that feels like a hack.
>
> Is that text channel necessary?  Is it safe to send it into a black 
> hole, or does the PeerConnection use it for signalling or something?
The requirement to have a data channel has been removed from the latest 
editors' draft.
>
> I can see that the channel might be useful for sending timely 
> app-specific data along with the media but it feels wrong to negotiate 
> it even if itís not needed.  For my application, itíd be better if I 
> could say upfront that I want to negotiate a PeerConnection with only 
> the given list of streams.
Agreed.
Received on Wednesday, 12 October 2011 16:15:22 UTC

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