Thanks for your patience Jason, let me try to clarify if you refer to these links you’ll find all the information regarding Live Streaming using Adobe Flash Media Server, additionally you’ll find information regarding HTTP Live Streaming also known as HLS Streaming which is the protocol to Live Stream to Apple devices … And when I say Live Stream, I mean streaming a live event in real time …
http://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/LiveStreamingAdobeFMS4.5.html
The tutorial above explains how to create a cloud formation stack for Live Streaming. The following link is where the urls are generated to embed in a player ect ..
http://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/LiveStreamingAdobeFMS4.5.html
By default, amazon gives you an embed code with their native player for flash that you can use on your site and also gives you a url for HLS for streaming to Apple devices using the m3u8 file format for implementation. By editing a cross domain file on the cloudformation stack that was created for the live stream, I can enable use of a third party player at my domain, such as JWPlayer ..
So I end up with 2 urls for my Live Stream Event … Flash and HLS .
My primary choice for end user is to use the url for HLS stream, and this is why ..
The premium edition which is a paid upgrade from the free edition of JW Player v6 supports playback of an m3u8 file ( HLS ) in a forced Flash mode which will allow desktops browsers to view the stream in all major browsers and the player will also auto detect if the device only supports HTML and will serve up the stream on the Apple devices using the Apple implemented m3u8 file format which is already designed to work on Apple devices as part of the Native and IOS platforms .. As described here:
http://www.longtailvideo.com/support/jw-player/28856/using-apple-hls-streaming
The player can also playback rss feeds with HLS urls in them as described here:
http://www.longtailvideo.com/support/jw-player/28843/loading-rss-feeds
I’m realizing while writing all of this that it seems editing the cross domain on the Cloud formation stack which would allow playback of third party players hosted at my domain will provide some security, since no one could use their own player for the content, but not sure how to protect the actual urls in the player, since someone could possibly re-construct a native embed code from the amazon examples.
I hope I was able to clarify better .. At the end of the day, securing a Live Streaming Event is what I’d like to do and wonder if there’s any insight from s2member about this.
And to go back to the beginning of this thread, protecting a properly formatted rss feed for jwplayer containing an HLS url was a natural thought that popped into my head as a possibility since we are protecting xml files already for our iTunes podcast .. But maybe there might be other options ..