4 ms·
This was done already, almost a decade ago. CNN.com used it and it was total hell for us, running a corporate LAN, because it flooded out our upstream bandwidt
by chrissnell 10y ago
This was done already, almost a decade ago. CNN.com used it and it was total hell for us, running a corporate LAN, because it flooded out our upstream bandwidth, especially when multiple people used it. Their product ended up being considered, basically, as malware:
https://arstechnica.com/business/2009/02/cnn-p2p-video-streaming-tech-raises-questions/ https://arstechnica.com/business/2009/02/cnn-p2p-video-strea...
How are you going to stop people from starving out bandwidth in large offices?
- semicolon_storm 10y agoDisable WebRTC on corporate computers? I'm assuming Peer5's solution falls back to servers when the browser doesn't support WebRTC.
- chrissnell 10y agoOK, sure, but what about other environments like hotels and colleges? This is going to be the bane of IT administrators.
- shacharz 10y agoThat's interesting, I know about Octoshape. But didn't know that in enterprise they actually made matters worse. The way our technology works is a bit like an 'onion' architecture. Users from the same corporation should communicate only with each other - and actually reduce the traffic on their internet connection - making the user experience better.
- chrissnell 10y agoThat's fantastic if that's the truth. I'm not sure how you deal with this. Big corps have many subnets so you need a reliable way to figure out who's link-local. Octoshape really was a disaster. During a major news event, many hundreds of employees could be live-streaming CNN and the effect was catastrophic.