Safari is the new IE

Re:Safari is the new IE by JoeAltmaier on Tuesday June 30, 2015 @10:50AM (#9805652)

All the important scalable features are incompatible - so-called 'bundling' where many streams use a single port etc. Aggregation of error feedback so an MCU can sensibly report bandwidth limits. Slow connect/reconnect times. No 'supernode' support. Pretty much anything that takes it from a toy with 3 or 4 p2p connections, to a product that can handle up to 100 streams with audio/video switching realtime through an MCU or P2P dynamically.

Other products can do this. WebRTC suffers from being based on RTP/RTCP and SIP-style signaling. There's not enough juice there to get the job done.

[ Parent | on HN ]

Re:Safari is the new IE by rockdoe on Tuesday June 30, 2015 @02:10PM (#9807282)

>All the important scalable features are incompatible - so-called 'bundling' where many streams use a single port etc.

AFAIK this is being fixed. Firefox should support the standard and Chrome is fixing their implementation to conform as well.

[ Parent | on HN ]

Re:Safari is the new IE by JoeAltmaier on Tuesday June 30, 2015 @02:26PM (#9807409)

Yes, 2 years after it was released. And there are many levels of bundling. Will they both support all of them? Will the MCUs follow quickly? The WebRTC landscape is a disjoint map of features and support that evolves very slowly.

[ Parent | on HN ]