Agreed that it is actually extremely simple to create something decent without even touching the server.  Here is a video on creating a basic application.  The application is located in the red5 swf's directory in 0.6.

Notice I don't even touch the server code.

btw, if the video doesn't load the first time. just refresh that page and it will.
http://www.newviewnetworks.com/nvnHome/blog/client/index.cfm/2006/10/21/Red5-Video-Tutorial-Basic-Example


On 11/9/06, John Grden < [EMAIL PROTECTED]> wrote:
I'm gonna pop up with some reality here:  Creating a new app in Red5 is very simple.  From creating a new folder in webapps, you can be up and running in seconds with:

streams
live broadcasts
recording
sharedObjects
rooms

and you haven't even touched a stitch of serverside code at this point.  I've done it - I know.  Now, if you want to get more granular, then you can add web.properties and the other files to get more specific about what IP that app is bound to etc, but that's as easy as editing the simple files (no more difficult that editing the xml files for FMS).

I think the conversation was getting out of touch with what's really going on and how we've setup Red5.  A flash developer doesn't need to know spring/java - I think the guys that DO know it get confused because of what they know.  but trust me when I say, i've set up several new apps, and I don't know JACK CRAP about Java/spring (Luke's seen my java skills - very upsetting ;)

anyway, I hadn't heard anyone stand up and say "we've been working toward the ease of use goal and pretty well acheived it" so I thought I would do it ;)

On 11/9/06, hank williams <[EMAIL PROTECTED]> wrote:
It sounds to me like we need to explore some use cases and make sure
that red5 *is* usable in a simple way that can be documented in a
getting started tutorial. If there are important things that require
in depth knowledge, the thing to do is to adjust the defaults and or
add functions that do all the things that are hard to do on startup.
There shouldnt be that much that needs to be configured to get
started. If what Dan is saying below means that to modify the location
a stream is saved to in java requires a lot of hoop jumping then that
probably needs to be smoothed over because that is fairly basic.

Perhaps Dan, you could put together a document that describes some of
the problems you had and solutions that you found. This is not for
documentation, but because I think it is important for everyone to be
able to see clearly, and in detail where the rough edges are. I think
it is very easy to become de-sensitized to how hard certain things
are. Your experience in getting things working is **incredibly**
valuable and could really help to make the product better. I would
hate to work hard to document something that is hard to do when it
would have been much easier to make an API adjustment that just makes
it easier.

Regards,
Hank

On 11/9/06, Dan Rossi < [EMAIL PROTECTED]> wrote:
> Chris Allen wrote:
> > I think that the API for Red5 can be confusing, but once you get the
> > concepts it's really not that bad. And at any rate, I'm not sure that
> > you need to know too much about Spring to build Red5 applications in
> > Java.
> Thats not the case, with the filenamegenerator bean for saving to custom
> stream paths (from my request :)) , i didnt get an easy explanation how
> to implement it, only just java jargon which luckily i understand, i had
> to get into the guts of the API to find the methods to override and what
> to put inside them ;) And still had to work out how things work and why
> im having problems etc, ive personally had to learn how red5 worked in
> the core to help me work out critical problems and also help make it a
> better app in the end :)
>
> > If one chooses they can hook up one main class via the
> > configuration and do the rest without the IoC container.
> >
>
> You obviouslly know what you are talking about because i have no idea
> what you mean here.
>
>
>
> _______________________________________________
> 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



--
[  JPG  ]

_______________________________________________
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

Reply via email to