Re: Non-browser interop

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.