[Red5] Refactoring Progress

[Chris Allen]

I concur, great job indeed!  Maybe we should just give the ten bucks
to Luke.  I think it will go a lot farther in Thailand anyway.  He
might even be able to buy three bags of peanuts and have some money
left over for a beer. ;-)

I will be glad to help with some of those unit tests, just let me know
which ones, where, how, etc...  Have you updated the SVN with this
stuff yet?

Also, in terms of a Skype meeting I'm down for this Friday in the
morning 8am EST?  I will send message to the core developers to get
that one going.

-Chris

On 11/2/05, Dominick Accattato <daccattato at gmail.com> wrote:
> Great job Luke.
>
>
> On 11/2/05, Luke Hubbard (luke at codegent.com) <king.selassie at gmail.com>
> wrote:
> >
> > Hi Guys,
> >
> > Ive been a little quiet over the past week so I thought I would send an
> update on whats been happening under the hood. We currently have two rtmp
> handlers the old IoHandler and the new ProtocolHandler. The old one binds to
> 1935 and the new one is on 1936. The new code IMHO is much cleaner with good
> separation of concerns. In the old IoHandler byte level stuff and processing
> was handled together. This was great for happy hacking as we worked out the
> basics of rtmp but quickly became a bit messy. I could have continued with
> the stream publishing on top of this but wanted to take a step back and
> build a decent foundation. Now in the protocol layer separates encoding and
> decoding and message processing. It also passes all method calls to a spring
> bean responsible for the application making the handler more compact. Oh
> also IO layer and the protocol layer have separate thread pools.
> >
> > Overview of new packages and classes.
> >
> > org.red5.server.rtmp (RTMPProtocolProvider, RTMPSessionHandler,
> Connection, Channel)
> > org.red5.server.rtmp.codec (ProtocolEncoder, ProtocolDecoder)
> > org.red5.server.rtmp.message (InPacket, OutPacket, PacketHeader, Message,
> ... subclass of Message for each data type)
> > org.red5.server.stream (StreamManager, Stream) UNDER DEVELOPMENT
> > org.red5.server.context (Client, BaseApplication, Application, Scope)
> >
> > Once the new code is at the same level of functionality (ie I have
> streaming working), I will probably move the old code into the attic or
> delete it all together. The only change which will effect the demo/test app
> is that now rtmp uri should point to the application not the service. To
> call a service within the AppContext you should pass the service name inside
> the ns.call so.. "getListOfFLVs" would become "demoService.getListOfFLVs". I
> think this should work with the old handler too. Can someone make this
> change to the fla, I don't have flash 8 yet :).
> >
> > So list of next tasks ( i will add to the basecamp site later)
> >
> >
> >
> > Get streaming working like before. (hopefully tonight)
> > Add flow control to the streaming, and calculate client bandwidth during
> streaming etc. (maybe tomorrow)
> > Add stream publishing (friday / weekend, can someone update the fla with a
> test for this).
> > Shared objects (next week, can someone write a test for this too)
> > Write more unit tests, esp for ProtocolEncoder, ProtocolDecoder (help
> welcome)Right I think we should arrange a skype meeting friday or early next
> week to discuss progress and spark outline / demo.
> >
> > -- Luke
> >
> >
> >
> > _______________________________________________
> > Red5 mailing list
> > Red5 at osflash.org
> > http://osflash.org/mailman/listinfo/red5_osflash.org
> >
> >
> >
>
>
> _______________________________________________
> Red5 mailing list
> Red5 at osflash.org
> http://osflash.org/mailman/listinfo/red5_osflash.org
>
>
>