[Red5devs] Integrating the Jetty6 to Red5 is done.
Dominick Accattato
daccattato at gmail.com
Wed Jan 11 15:42:02 EST 2006
Somebody give the kid rights to commit. I think we need to immediately work
on an admin web interface for deploying Red5 server side applications. Of
course we could probably use jetty's admin interface but, we will want to
make it as simple as possible for users to deploy their applications and a
Flash developer won't want to add all these j2ee deployment descriptors
themselves. So for instance, when someone creates a server side
application. They just hit the admin interface...
http://<domain>:<port>/red5/admin/index.jsp
from there, they see an upload button where they can grab their server side
script and their flash application and just upload it. Next the admin
interface deploys the application and gives the user a context path where
the application is deployed... (of course the app will be hot deployed so
the server won't need a restart). The user then hits their flash front end
and bam.. connects to red5.
I won't go into all of the advantages here of using this method. I think
that those of us who are working on this are still fleshing out the design
of such an architecture. Plus there are soo many advantages. I don't want
to sound like a sales pitch here.
The problem comes with deployment. Those j2ee people out there know that
deployments are painful with java. So, websphere and others built
containers into the dev environments so that the developers wouldn't have to
deploy to a full j2ee appsserver just to test. We will need to figure out a
friendly way for developers to test their content on Red5.
This could be where other tooling comes in or even a little innovation!!!
Keep those thinking caps on.. were venturing into unknown territory.
On 1/11/06, Luke Hubbard (luke at codegent.com) <king.selassie at gmail.com>
wrote:
>
> I would be interested to hear if anyone thinks the fcs way has advantages.
> -- Luke
>
> On 1/11/06, Dominick Accattato <daccattato at gmail.com> wrote:
> >
> > Ok, yes this is a logical evolution. I just want to point out a
> > similarity between this and another well known web application that sits on
> > an application server. Coldfusion Enterprise uses this type of
> > configuration. For instance, you deploy the coldfusion administrator as a
> > ear or war file. Then when you log into the administrator, you deploy your
> > coldfusion wars. So this step will help us build the security into a web
> > type interface. Good thoughts, lets move on!
> >
> > On 1/11/06, Luke Hubbard ( luke at codegent.com) <king.selassie at gmail.com>
> > wrote:
> >
> > > Hi Jokul,
> > >
> > > Thanks for doing this. John will sort out commit rights for you when
> > > he can. For now just hold this code.
> > >
> > > Interesting approach, but I like it. I guess each host would connect
> > > to a global instance of red5 and be given access to its red5 host
> > > context. I'm thinking this needs more thought since we want to be flexible
> > > and able to work in a number of configurations. At the moment we
> > > are following the fcs way of doing things having a hosts directory and
> > > applications off that all mapped using directory names. This works but
> > > doesn't gel well with webapps / servlet engines. I guess its two ways of
> > > modeling the same thing. Anyway I've just had a chat with chris and think
> > > its time for us to change. So here is how I would like it to work.
> > >
> > > 1. Standalone Red5 with embedded Jetty. The default setup.
> > >
> > > Red5 Standalone loads and starts Spring
> > > Spring loads /conf/red5.xml and starts up Global Services, Mina,
> > > Jetty, etc.
> > > Jetty loads /conf/jetty.xml and starts up a number of webapps (each
> > > with its own classloader, important for hosting and security).
> > > Inside each {webapp}/WEB-INF/red5.xml there is a per webapp context.
> > > This context scans for {webapp}/*/RED5-INF/red5.xml files and adds
> > > these as red5 applications.
> > >
> > > Some example paths.
> > > /conf/red5.xml < global red5 config file
> > > /example/WEB-INF/red5.xml < per webapp context ( currently called host
> > > )
> > > /example/chatroom/RED5-INF/red5.xml < app context
> > > /example/chatroom/RED5-INF/services/app.js < javascript service
> > > /example/chatroom/images/logo.jpg < static files available over http
> > >
> > > Some more example urls.
> > > http://localhost/example/chatroom/images/logo.jpg
> > > http://localhost/example/gateway < remoting gatway
> > > rtmp://localhost/example/chatroom < connect to chatroom using rtmp
> > >
> > > 2. Red5 deployed to another servlet engine as a single webapp.
> > >
> > > Take the webapp out of Red5 Standalone merge the red5.xml files,
> > > remove the jetty entry and copy red5/lib/* to webapp/WEB-INF/lib. Deploy to
> > > tomcat or weblogic or whatever.. In theory this should work. We could even
> > > have a nice war export tool.
> > >
> > > Let me know what people think...
> > >
> > > Right I gotta run.. thanks again for your work.
> > > We really do need to get together for a good chat.
> > >
> > > -- Luke
> > >
> > > PS: Have you signed up to the dev list?
> > > http://osflash.org/mailman/listinfo/red5devs_osflash.org
> > >
> > > I have copied the list in on the reply to this email, I think its good
> > > if everyone is aware of what people are working on and I want to get
> > > people's input on this.
> > >
> > > On 1/11/06, tian xue <tianxuefeng at gmail.com > wrote:
> > > >
> > > > Hi Luke
> > > >
> > > >
> > > >
> > > > I have completed in integrating the Jetty6 to Red5. Steps
> > > > list as below:
> > > >
> > > > 1) Download newest Jetty6 from
> > > > http://heanet.dl.sourceforge.net/sourceforge/jetty/jetty-6.0.0beta7.zip
> > > >
> > > > 2) Copy Jetty library from directory "lib" and "lib/jsp" to
> > > > Red5's library path.
> > > >
> > > > 3) Copy Jetty configuration file "etc/jetty.xml" to Red5's
> > > > "conf", and modify as below.
> > > >
> > > > Change all "etc" to "conf".
> > > >
> > > > Remove "UserRealms", if want to reserve this,
> > > > also need copy "realm.properties". This is optional.
> > > >
> > > > If want to start HTTPS SSL listener, then need
> > > > copy "keystore". This is optional.
> > > >
> > > > 4) Modify "red5.xml".
> > > >
> > > > <!-- httpServer: This is the httpserver-->
> > > >
> > > > <bean id="httpServer" class="org.mortbay.xml.XmlConfiguration "
> > > > init-method="newInstance">
> > > >
> > > > <constructor-arg>
> > > >
> > > > <bean class="java.io.FileInputStream">
> > > >
> > > > <constructor-arg value="conf/jetty.xml"/>
> > > >
> > > > </bean>
> > > >
> > > > </constructor-arg>
> > > >
> > > > </bean>
> > > >
> > > > 5) Copy Jetty's directory "webapps" to Red5. We can delete
> > > > this directory; add the files relative with our project.
> > > >
> > > > For the war file, we can put it in "webapps", and modify
> > > > the "jetty.xml".
> > > >
> > > >
> > > >
> > > > I have no rights to check in the modification, would you
> > > > please help me check in the modification?
> > > > What do you think of this? Is there have any thing should do better?
> > > > And is there have any other task i can do next? Please let me know!
> > > >
> > > > Thanks very much!
> > > >
> > > >
> > > >
> > > > Best Regards
> > > > Jokul Tian
> > >
> > >
> > >
> > > _______________________________________________
> > > Red5devs mailing list
> > > Red5devs at osflash.org
> > > http://osflash.org/mailman/listinfo/red5devs_osflash.org
> > >
> > >
> > >
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://osflash.org/pipermail/red5devs_osflash.org/attachments/20060111/4837ffee/attachment-0001.htm
More information about the Red5devs
mailing list