John Grden wrote: > > streams > live broadcasts > recording > sharedObjects > rooms > > and you haven't even touched a stitch of serverside code at this point. Sure the API is setup in a way all u have to do is extend the application adaptor with no extra methods needed and away you go, but how many people here just need that ? I doubt it, it requires more effort than that to build a proper application really. Ie for streaming i have to use the stream aware methods to tell currently connected subscribers playing a trailer to connect to the live stream so requires a call, and obviouslly the custom archive path. But anyway, they are already setup in the example apps so copying isnt an issue, its when you have to start customising which is a problem to work out where to access data from what methods etc, ie obtaining the proper data for logging streams which FMS does for you already. There was talk about a stats API but nothing yet.
> 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). It is when you now have 3 or 4 different cache methods to use, which require to know the cache API to play with the settings required to make large file stream support possible atm. Aswell as tweaking the java command to add memory flags. _______________________________________________ Red5 mailing list [email protected] http://osflash.org/mailman/listinfo/red5_osflash.org
