Almost all software is difficult (rough) to use as its first created. It's not until developers make a few passes before things start to smooth out. For instance, many open source projects use xml files to configure up their software. Then a few versions down the road a gui to that xml file is introduced. The same goes for Red5. At first creating a decent application will take some understanding of the technologies behind it. However, these will subside when more automation is introduced to the workflow.
Now, to get this thread back on topic. I suggest Hank create a new thread with what he needs, and the ranting can continue on this thread.
Hank... "YOU CAN DO IT!!"
On 11/10/06, Dan Rossi <[EMAIL PROTECTED]> wrote:
Michael Klishin wrote:On Fri, 2006-11-10 at 13:59 +1100, Dan Rossi wrote:
Yes, to lighten up the server i have to modify a great deal of it,
remove the demo apps and configurations etc for production environment
and just load the ones required.
Great deal like what? Install it as WAR to your servlet container of
choice and move applications context files, properties (that you need or
not) and any other files under /red5/WEB-INF
woosh over my head, servlet of my choice ? why do some of us need to worry about that, as i said before im not a java guy and leave defaults as default :)
_______________________________________________
Red5 mailing list
[email protected]
http://osflash.org/mailman/listinfo/red5_osflash.org
--
Dominick Accattato, CTO
New View Networks
www.newviewnetworks.com
_______________________________________________ Red5 mailing list [email protected] http://osflash.org/mailman/listinfo/red5_osflash.org
