I plan to use red5 to handle live audio/video streams in any number of chat rooms. I will not be doing anything else in Flash except handling live audio/video, so basically means forwarding to clients in the same room, with a little server side logic to verify permission to connect, and to forcibly disconnect someone. Something along the lines of:
http://gregoire.org/2009/04/07/on-demand-room-scope-creation/
All client-server messaging and app logic will happen in a normal html page using Ajax to our servlet running under glassfish. No UI or remote calls will be done in flash -- just the live audio/video streams.
Given that glassfish is already going to be running, I would like to know whether I can expect better performance with Red5 standalone or running as a WAR under glassfish.
From reading about deploying red5 as a WAR it seems that there might be some performance penalty for an "External Application" going through the AMFTunnelServlet. (
http://trac.red5.org/wiki/Documentation/UsersReferenceManual/Red5CoreTechnologies/02-Deploying-To-Tomcat )
Is there an "external application" performance penalty? If so, can I deploy as a WAR and make the red5 portion of my app an "internal" one by adding it to the war? Is there some other approach that I should be looking at? The docs are heavily focused on running red5 standalone, which is certainly an option, but I worry about memory usage if I have two Java VMs running server side.
I'm brand new to red5 and j2ee and would greatly appreciate any advice on the best architecture.
_______________________________________________
Red5 mailing list
Red5@...
http://osflash.org/mailman/listinfo/red5_osflash.org
