3 ms·
It's awkward that in 2013 we have to complexify design to this point : "Streaming video through WebSocket (thus over http upgrade) through a plain-tcp-to-webso
by paraboul 13y ago
It's awkward that in 2013 we have to complexify design to this point :
"Streaming video through WebSocket (thus over http upgrade) through a plain-tcp-to-websocket-proxy on top of...".
It feels over-engineered and like TCP-Sockets are a revolution. I know, we can't easily expose plain-socket because of security but still... What's next? UDP for 2018? Socket-binding for 2022?
(Nice work though)
- makomk 13y agoWell, traditionally this would be done using something like Flash and RTMP, but Flash is dead on mobile - Apple considered it too CPU and battery hungry and a poor user experience, so they banned it. Hence MPEG decoders implemented in JavaScript.
- paraboul 13y agoI think you missed my point. I'm not criticising what phobolabs (who is very talented BTW) has done or what any end-developer is doing. It's just crazy how the standard is slow to come up with new basic APIs. I mean, you can make a P2P video streaming application since 1995 using straightforward architecture in a desktop App using less cpu, less middleware and less engineering.