I'm reading the source, one thing I can hardly understand is that it has a room concept in some java files, like the IApplication, is it concrete for future use??
Well ScopeHandler is core so can be considered concrete. IApplication interface doesn't do much at the moment, its really just a list of higher level methods to those found in ScopeHandler. The methods will probably not change that much but will develop as we add to the api. The base implementation ApplicationAdapter also provides more high level api functions and can be extended when you create your app or can be used on its own if you just want a default handler capable of shared object and streaming.
This release we are focusing on the streaming and messaging internals of the server so you probably wont see much work done on the application support site of things. That will come with 0.6. Protocols, shared objects, and streaming are quite separate concerns from application support, so we are considering separating development. The core server will have a concrete set of lower level api classes and a separate application framework which sits on top. This will hopefully keep the two things server and app framework from being coupled and allow for different application frameworks to support different types of users.
Please let us know what you would like to see from a the api / app framework side of things and we can asses how we can improve the api.
-- Luke
PS: Please snip your replies, quoting the whole digest is rather heavy.
_______________________________________________ Red5 mailing list [email protected] http://osflash.org/mailman/listinfo/red5_osflash.org
