Thanks Bill. I've started a thread on the list for this discussion. :-)
On 4/2/07, Interalab <[EMAIL PROTECTED]> wrote:
This discussion is very good news and I'm interested in helping. How do you propose to start accumulating the use cases? Would it be helpful to set up a form that people can fill in - a series of questions so we can get all relevant information for each use case? I'm willing to build and host a form and data collection if that helps. Bill Steven Gong wrote: > I agree that we need to start from the analysis of the overall usage > models and then can we make design decisions on how to remodel the > system. We can startup a thread to discuss different usage models and > user requirements. Then we can make a summary and post the result to > wiki. > > I've already reviewed our code base and got the overall picture of our > current status. IMHO modularization is always needed for a project to > succeed and remodeling or refactoring can proceed concurrently with > the discussion. > > Finally the document for the architectural design is surely crucial. > Michael has done a good job on code documentation and I will > contribute some time to document the design continuously. > > On 4/2/07, *Alexander Zhukov* <[EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>> wrote: > > What I would do first is take a piece of paper and write down a > list of features people need and how they can be accomplished > right now. > In both modes server (what red5 is now) and library (what > red5-minimal offers). > E.g. > Q. I need to stream VOD > A1. setup red5 server, change config in the following places 1, 2, 3 > A2. use the following class from library (red5-minimal or > red5-core), set the following fields > > Afterwards ensure all the questions and solutions are in wiki, I > am not red5 old timer but I see people complaining about the lack > of documentation. > > Third step would be to think what should be changed to have all > the questions answered, > that's when, in my opinion, refactoring might or might not > (depends on features asked) take place. > > PS. good overall architecture document is bitterly needed (have I > missed a link in wiki?), > since even after repackaging red5 into red5-minimal I dont have > the-big-picture of red5 in my head. > > On 4/2/07, *Steven Gong* < [EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>> wrote: > > Thanks a lot, Alexander. > > Luke and I are thinking of remodeling Red5 to meet different > requirements recently. The key point is that our customers > might not need all features we provide. Some might not need > the application framework. Some might only want to stream > VODs. Some might only need SharedObjects. So it makes much > sense to make a red5-core as small as possible and make other > modules like application support, streaming and sharedobject > as add-ons. Your red5-minimal is quite insteresting and the > idea is, to some extent, similar to our considerations. Maybe > you can contribute some efforts in this remodeling work if > you'd like. > > Thanks again for your great work. :-) > > > On 4/2/07, *Alexander Zhukov* < [EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>> wrote: > > Yes, this is the hardest part, I cant stop thinking about. > I'm glad you mentioned it. > Actually the modifications we've made to red5 itself are > not major (some constructors added, some factories used > instead of Spring app context) > So the best possible solution would be to merge those > changes into red5 trunk and write a separate build.xml (or > add a task to existing one) to generate red5-minimal.jar > In the other case, if red5 team finds out that > modifications are too invasive, I would be very grateful > if we coordinated to release red5 and red5-minimal at the > same time. > That is when you decide there's a time for release, > announce it in the mailing list a week or so before so > that we can pickup the changes. > As usual, if somebody is interested to keep the source in > sync more often than every release the source of > red5-minimal is there, if it is required we can setup a > separate repository or commit all the source code as a > red5 branch. > > Cheers > > On 4/2/07, *Chris Allen* < [EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>> wrote: > > I can see how this is going to be very useful to > people. How do you plan to maintain this version? In > other words keep it in sync with the changes we make > to Red5. It might make sense to coordinate with you > for our releases so that you can get out a version at > those times too. > > Anyway, great job and thanks! > > -Chris > > On 3/31/07, *Alexander Zhukov* < [EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>> wrote: > > Hi All! > > We have put together a small and embeddable > version of red5 - red5-minimal. > You might find red5-minimal useful if dont need > all the features of red5, but streaming and rtmpt > flashapp to server communication. > > red5-minimal is a small subset of red5 server > which is based on red5-0.6rc2. > The main goal of red5-minimal is not to substitute > red5 but to provide a small standalone jar and > easy to embed class file to run red5 from within > your application. > > red5-minimal is configured entirely from your java > code, so you can think of red5-minimal as a > library not a full-fledged server like red5. > > Everybody is invited to check out red5-minimal > code at http://oss.viewdle.com/red5-minimal/ > > Comments, ideas, criticism are appreciated, if > you find red5-minimal useful or absolutely ugly > please tell. > > > _______________________________________________ > osflash mailing list > [email protected] <mailto:[email protected]> > http://osflash.org/mailman/listinfo/osflash_osflash.org > > > > _______________________________________________ > Red5 mailing list > [email protected] <mailto:[email protected]> > http://osflash.org/mailman/listinfo/red5_osflash.org > > > > _______________________________________________ > Red5 mailing list > [email protected] <mailto:[email protected]> > http://osflash.org/mailman/listinfo/red5_osflash.org > > > > > -- > I cannot tell why this heart languishes in silence. It is for > small needs it never asks, or knows or remembers. -- Tagore > > Best Regards > Steven Gong > _______________________________________________ > Red5 mailing list > [email protected] <mailto:[email protected]> > http://osflash.org/mailman/listinfo/red5_osflash.org > > > > _______________________________________________ > Red5 mailing list > [email protected] <mailto:[email protected]> > http://osflash.org/mailman/listinfo/red5_osflash.org > > > > > -- > I cannot tell why this heart languishes in silence. It is for small > needs it never asks, or knows or remembers. -- Tagore > > Best Regards > Steven Gong > ------------------------------------------------------------------------ > > _______________________________________________ > 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
-- I cannot tell why this heart languishes in silence. It is for small needs it never asks, or knows or remembers. -- Tagore Best Regards Steven Gong
_______________________________________________ Red5 mailing list [email protected] http://osflash.org/mailman/listinfo/red5_osflash.org
