Thanks for the great responses, guys. On 9/11/07, Matt Aimonetti <[EMAIL PROTECTED]> wrote:
> Is there a format you have to use? Do you need to do progressive, real > time streaming, both? Is your client ok with forcing the user to have a > specific plugin/app installed? All great questions. I'll be fleshing them out as we go through the requirements of the project. Honestly I'm still crossing my fingers that they'll just let customers download the video, Peepcode-style. We'll see. I don't think a normal flv player would work for you. Otherwise anyone > purchasing access to a stream once could simply get the url for the flv and > pass it to other people. (and if your file naming is based on the video id, > one can guess the urls) > Yeah, I'd use some sort of expiring token at the least and just not stress too much about people trying to steal stuff. Flash player 9 just added support for h.264 and AAC+ which I would strongly > recommend to use if your client is ok asking all users to update their flash > player if needed. > Duly noted. I'll add that (and all the other fantastic links in this thread) to my list of stuff to research. I would also build an authentication system using a required token to watch > a stream. Use Flash Stored Object to save a UUID for the client so the link > would only work on your client's machine. (Flash Stored Object don't expire) > > How much flash-fu would all this require me to have? Because I have none, heh :P -- Nick Zadrozny • beyondthepath.com
_______________________________________________ Sdruby mailing list [email protected] http://lists.sdruby.com/mailman/listinfo/sdruby
