mrchrisallen at gmail.com
Thu Nov 9 18:03:34 EST 2006
On 11/9/06, Dan Rossi <spam at electroteque.org> 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 :)
Well, as I said before, for simple applications and getting started
you don't need to know that much. We are talking about getting
started, not creating a way to save you FLVs to another path. At any
rate, I've been a bit out of touch with the code lately as my time on
the project has taken me elsewhere. I could be totally wrong about all
of this. However, the idea behind building the Red5 API was to make
things simple to use. If it's not, then perhaps we need to improve it.
> > 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.
Haha! Yeah, what I'm saying is pretty simple, I just didn't do a good
job of explaining it. What I meant is that you can hook up only one
bean that does everything for your application.
More information about the Red5