On 6/15/06, João Saleiro <[EMAIL PROTECTED]> wrote: > > I've been reading about Red5, and it seems that it would solve both > problems: the first, because of Red5 intrinsic characteristics, and the > second because it would allow development on JAVA. >
It does indeed sound like a good fit for you. > > > Red5 could be an excellent solution for our case, but it's not stable yet > and I don't know almost nothing about it. So, my questions: > > 1) How does Red5 behaves in high traffic situations? Does it require a > web server with special characteristics? Even for streaming video? > As Red5 is in its early stages still, a lot of this is unknown. However, I can tell you a few things. Red5 by default is running Jetty (the web server in this case) for HTTP traffic. Jetty is well tested and a proven solution for this type of thing. I don't believe that you will require any special hardware or software to run Red5 other than JVM 1.5. > > 2) Our hosting is one of those plans where accounts have one default > configuration provided by the host, so we can't change it. Apart from PHP, > MySQL, Perl, etc, etc (the usual things), we have also Tomcat. If we would > like to use Red5, we would need a more liberal solution, were we could do > our own configuration, right? I've seen the following on the roadmap for 0.6 > version of Red5: "Available in standalone and WAR versions". Does this mean > that Red5 would work with my current hosting configuration (via TomCat)? > (Sorry for being so lame on these subjects, I'm just a developer K) > Like I said above, Red5 uses Jetty by default, but we are looking to provide a way to deploy Red5 applications as .war files. Tomcat would be a container that it could run within. Another approach may be to have Apache's http server sit in front of Jetty for higher traffic situations. So, it sounds like it may work for you with your default hosting provider's configuration using TomCat. > > 3) From which version of Red5 could we start thinking on developing our > final solutions? Will 0.6 be fine for this? Is there a planned release date > that for this version? > Yeah, I think 0.6 would be fine for starting real development. The API should be pretty stable by then and the changes will be more bug fixes and performance enhancements. We can't estimate a release date for that though, as we are all working on Red5 during our free time. > > > Considering the following: > > > > - Our next project will start on the middle/end of July; > > - It will require sync between clients (i.e. changes made using one > client would automatically change the others, preferably without waiting for > the next pool); > > - It may need video streaming, and even possibly video chat between > clients; > This sounds like a really cool application, and well suited to using Red5. > - Our hosting is very limited: we can't change the base > configuration of our accounts, but we have TomCat installed; > We should be able to get it to work in this case, as long as they are willing to open up certain ports for RTMP. > - Our project will be probably very visited. There is a possibility > that it's URL will appear sometimes on the television and radio, resulting > on periods with very large traffic demands. > Yeah, like I said, we don't have any statistics on this yet, but this doesn't seem unreasonable. > - We need a mature solution for the server side, with sync between > code and UML, so JAVA would be preferable; > Obviously Red5 server-side applications can be written in Java. > > > Which solution would you choose, between Red5, openAMF or AMFPHP to solve > our case? > I'm a little biased, but given you are interested in real time communication, shared objects and possibly streaming video, Red5 seems like a good choice. The obvious concern is that it's not been tested and is still young. You of course can still build your application logic to use Remoting and Java on the server. If you keep the tiers of the application well isolated you will be able to switch between OpenAMF and Red5 with little trouble. So, Java seems like a logical choice for you. I highly recommend using Spring as well, as it does help keep you coding to interfaces and putting little dependencies in your code. > > I know that openAMF and AMFPHP haven't the possibilities that Red5 has, but > if one of our limitations (i.e. project start time before stable release of > Red5, server limitations, etc) doesn't allow Red5 adoption, we have to cut > on some requirements and chose between openAMF and AMFPHP. Which one is > preferable? Yeah, use Java. see above. > > Thanks once again for your help! > > No problem. If you have more specific questions feel free to ask here or join the Red5 list and post them there. _______________________________________________ osflash mailing list [email protected] http://osflash.org/mailman/listinfo/osflash_osflash.org
