First, we really don’t support being an HTTP origin for a CDN. It is a feature we plan on adding sometime in the future but it is not a use case we have designed for or tested.
That being said, it is most likely possible to make it work. For San Jose and Smooth streaming the playlist and chunk URLs are already relative. It is only Cupertino streaming that by default has absolute playlists.
Is it a feature being considered for Wowza 3? It seems to be more or less working as is so I am curious as to what additional stuff you are planning on adding.
I tested my connections and you are right, it does appear the chunks themselves are being pulled and distributed through Edgecast. Connection-wise I don’t appear to be seeing multiple connections - is there a specific log file/way I can check this in Wowza? I am using the AWS version.
As for working, I’ve had a live test stream running off a camera in my building for 4 days straight now and it hasn’t dropped, not for Silverlight or Apple. I even have a flash client (JW Player) connected to the Cupertino stream using JW Player’s alpha AdaptiveStream module (testing it with them) which allows Flash to connect to m3u8 playlists, and even it’s working well. I plan on doing heavier testing with multiple streams later but thought you guys would like to know so far, so good.
Let me know if there’s an easy way to see how many connections are being made to the Smooth Streaming manifest.
Update: I figured out the log part; when I initiate a connection on multiple remote clients, the only connection I see in the Wowza access log for the Smooth stream is from Edgecast’s pull source, which is as it should be. Is there somewhere else to check or is that more or less it?
Does the load test work with HTTP live streams or just RTMP live streams? The response above is unclear on that point.