load balancing is a far more complex subject Yes I know, I'm running my own little Wowza cluster of a couple dozen hosts, so I have faced the same problems. ;-

load balancing is a far more complex subject Yes I know, I'm running my own little Wowza cluster of a couple dozen hosts, so I have faced the same problems. ;-) If the customer of the CDN is unwilling to lift a finger Okay, I guess that's an argument - although I'm not sure to what degree this can be held against the protocol. As for the other problems you mention (apart from the RAM issue), I can see how they can be problematic in a multi-tenant/CDN environment. I'm just not sure I'd want to see a transport-protocol packed with all those concerns, as that would result in a lot of bloat and half-baked trade-offs (i.e. quite possibly even worse than RTMP). While some basic building blocks (e.g. the 302) would indeed be helpful, we have so far had good luck with encoding meta-data into the URLs (crypt/hmac) and handling the logic on the origin. Anyways, thanks for the insight. It's always interesting to learn how other people use and look at these things.