undefined | Better HN

0 pointsstackedinserter4y ago0 comments

Send RTP via TCP then, it will fix all problems you mentioned.

BTW what is so complex in RTP?

0 comments

> Send RTP via TCP

Please don't. TCP is entirely inadequate for streaming because of head-of-line blocking behavior. Nobody use RFC4571 for that very reason.

You can make TCP/HTTP work for streaming, but that usually involves developing some fragile system that does chunking, buffering, and retries. Probably implemented as a sizeable pile of custom idiosyncratic Ajax.

stackedinserterOP4y ago

Just a friendly reminder that the alternative is sending MP4 or MPEGTS chunks via HTTPS with terrible overhead and latency. Also, we're discussing it in a thread about something that converts camera stream into MJPEG.

> You can make TCP/HTTP work for streaming, but

RTMP works via TCP just fine, although it's not the best protocol either (but better than HLS)

> sizeable pile of custom idiosyncratic Ajax

I don't want it to be handled in JS. Let's just add RTP/RTMP/SRT/whatever support to browsers. They already include full ffmpeg libraries anyways.

j / k navigate · click thread line to collapse