News for hackers. Stuff that matters.

toptalgergely

You mean the apple protocol? Not sure, but I looked at that when I designed it. What I did was just the most intuitive
I'm glad you liked it, it was a lot of fun. I also implemented on the fly transcoding, but that's probably for a different article.

For the tech, well really at that place we used pretty much what everyone else did. Not a lot of big secrets, as far as I know the porn driving the tech revolution thing is ridiculous.

EU traffic in our case about ~1.2x the US traffic.
Unfortunately that's the case. I heard really good things about wowza these days. Not open source but a lot of things are open and flexible. Also back then red5 was also an ok alternative, not sure if that's still the case.
No, not IP multicast. Imagine it as a web server that serves FLV files which always start at the current stream position. This is what it did.

Actually bringing up the proxy issue is interesting. I'm not sure if it does. Essentially forbidding all caching would make it play nice.

Original writer here.

Actually this was a website which streamed online broadcasts live from people, like ustream does but with adult content. Some broadcasts could be hours long.

Author of the original post here.

>It's not clear what the article means by "repackaging" a stream or "pointers" to tags (especially in the diagram that shows tag pointers being transported between users).

By repackaging I meant extracting the FLV tags which pretty much travel in the same format as in an FLV stream (.flv file) if memory serves well. Pointers to tags refer to the internal implementation. I took the FLV tags out of the RTMP stream, which resulted in an almost complete FLV stream. With the proper header prepended to it you could save it as a file and play it or stream it and play it. That's just what I did, created a header for every new user, and after that was sent I could just stream the FLV tags from a common buffer. The users had pointers that pointed in this buffer so after the header is sent it was true multicasting.

> So I'm not really following this. Is this cutting out the RTMP entirely for receiving clients, and instead sending the FLV down via another transport, like HTTP or whatever? Or is it more of, "I wrote my own RTMP streaming server in C and Python", along with some implementation details which I'm not understanding? (Not that there's anything wrong with doing so. Options are limited in the streaming- server space.)

Yes. From the source RTMP stream I extract the FLV tags, which I could use to multicast. Sending the same RTMP stuff to every user would not work, but I can easily send the FLV tag stream over HTTP if I send the crafted header first.

I hope that helped