[YouTube-API] Understanding Architecture of Youtube

Hi....

   I've challenge to make a private youtube at my company...(but can't be youtube, because we need to have the control) and I've reading about Media Server's, Streaming.... 

   My target now is to plan the architecture considering the resources necessary and the problems related for the situation bellow:

• as youtube thus, need to conversion to unified format (like flv)
• in this case, I'm thinking to implement as plus an applet to process this transformation local at client machine
• as processing is heavy I'm trying to calculate the necessary resources (servers, clusters, replications..)
• find max size that can fit the need and understand the affect to architecture about storage...
• play video on demand (streaming it)
• be able to download it
• only authorized people will see or download it
• play and upload audio, need to convert to an unified format (like mp3)

The client is an application that will have multiple acces (would be in national context...), and our environment is Java, so need to understand  the best technologies for this situation.

I'm reading now for this:

• http://www.red5.org/ 
• and I'm considering www.wowza.com 
• http://flowplayer.org/
  
• http://www.xuggle.com
  
• HTML5 and Flash for client play

Any sugest I'll appreciate!

Thanks!

Renato.

--
You received this message because you are subscribed to the Google Groups "YouTube APIs Developer Forum" group.
To view this discussion on the web visit https://groups.google.com/d/msg/youtube-api-gdata/-/-J4NhN2uZpYJ.
To post to this group, send email to youtube-api-gdata@googlegroups.com.
To unsubscribe from this group, send email to youtube-api-gdata+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/youtube-api-gdata?hl=en.