Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Peer5 uses webrtc datachannels and runs on top of existing dash/hls streams


still doesn't scale efficiently. http based streaming is the only reliable way to get economies of scale. The cpu cost per webrtc socket is high compared to a cache-hit for a static resource. Not to mention that WebRTC is way more cpu intensive client side compared to hls/dash which has kernel/hardware offloading.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: