News for hackers. Stuff that matters.
Re:Hello Firefox, this is Chrome calling by drivebyacct2 on Monday February 04, 2013 @08:45PM (#5168527)
They recently appeared behind an about:flags flag. :)
Re:Hello Firefox, this is Chrome calling by comex on Monday February 04, 2013 @08:50PM (#5168548)
Well, when I heard that WebRTC was in Chrome stable I thought this must surely include DataChannel, since it's simpler than a full-blown video stack. So although it being behind a flag is better news than it not being there at all, I was still pretty disappointed when I read that page :)

edit: also, I don't see it as an about:flags flag.

edit 2: I should just tunnel data through video then, what could possibly go wrong?

Re:Hello Firefox, this is Chrome calling by pthatcherg on Monday February 04, 2013 @11:13PM (#5168993)
It's not quite that simple. We (I work with the Chrome team) have an RTP-based data channel (sort of what you call "tunnel through the video" already in Chrome), but it provides no congestion control or reliability. To provide those, the IETF has proposed as the standard to use SCTP. Firefox has already integrated SCTP into their implementation, and we're working to get it into Chrome. So, you can start using the API now, but it'll get much better soon.
Re:Hello Firefox, this is Chrome calling by carterschonwald on Thursday February 07, 2013 @03:25PM (#5184303)
Sctp is a pretty cool protocol. I'm actually planning on including it as part of a user land network stack I'm slowly working on.
Re:Hello Firefox, this is Chrome calling by drivebyacct2 on Tuesday February 05, 2013 @08:02AM (#5170408)
Sorry, I forget not everyone is on the Dev channel, but I have this available:

Enable RTCDataChannel. Mac, Windows, Linux, Chrome OS, Android: Enable experimental RTCDataChannel for peer-to-peer data communications. Disable

Version 26.0.1397.2 dev