I think I see where you are going with this, and I'm not sure what you want is exactly posssible. However, having separate instances of the Red5 web application running within Tomcat should accomplish this for you. It seems like a lot of duplication, but I think it's the best approach so far.
Having Red5 run as an individual web app makes it easier for us to maintain the code base. Essentially the WAR version is the same as the standalone, the standalone just comes preconfigured with Jetty as the servlet engine. Does this make sense? We of course appreciate any feedback that you have on the structure. -Chris On 2/13/07, Interalab <[EMAIL PROTECTED]> wrote: > Thanks for the link. I'm not sure if I should comment on that thread or > just throw my reaction out here. Please let me know if my comments > merit adding to the wiki discussion. > > I think I understand the concept of the proposed structure. Ideally for > us would be a structure that encapsulates the Red5 server as a > standalone server that only contains the core Red5 server. Then, if I > want to add an application that uses the Red5 server, I would prefer to > have it as a separate webapp that encapsulates just that application and > stream folders, but uses the Red5 server running in the same container, > but in a different application context (I don't even know if that is > possible). > > Red5 Server: > - webapps > - red5 > - index.jsp > - WEB-INF > - lib > - classes > - web.xml > - server > - red5.xml > - red5.properties > - myApplication > - index.jsp > - WEB-INF > - lib > - classes > - web.xml > - streams > - _persistence > - _temp > > With this structure, I could hot deploy multiple applications without > causing a re-deploy or re-start of the core server or other applications. > > Am I showing my ignorance? > > Joachim Bauch wrote: > > Hi, > > > > Interalab schrieb: > >> I'm particularly concerned about the new app structure. Will it be > >> shared with the list for comment before it's built into the trunk - I > >> hope? I know I'm not a dev on this project but a significant change > >> to the structure, especially if it doesn't comply with expected > >> 'norms' in the J2EE and, in particular, the Tomcat world, could > >> really affect our ongoing development efforts. > >> > >> I guess not knowing is what's making me nervous - even though I have > >> no right to complain as we've only been testing the releases and > >> sharing our results and not contributing any code to the project yet. > > > > the new app structure is discussed in the wiki: > > http://jira.red5.org/confluence/display/appserver/Simplified+server-side+application+structure > > > > > > Joachim > > > > ------------------------------------------------------------------------ > > > > _______________________________________________ > > Red5 mailing list > > [email protected] > > http://osflash.org/mailman/listinfo/red5_osflash.org > > > > _______________________________________________ > Red5 mailing list > [email protected] > http://osflash.org/mailman/listinfo/red5_osflash.org > _______________________________________________ Red5 mailing list [email protected] http://osflash.org/mailman/listinfo/red5_osflash.org
