This is just my observation, but I detect the early signs of a little mission creep setting in with Red5. When I first discovered Red5 it had gotten off to a flying start with a working rtmp streaming server. Maybe it's not my place to say, and this if for the projects leaders to decide but I think there's a little creep setting in from what I perceived was the original goal. I see a lot of talk on the list about porting, adding non core features and doing a whole load of things that aren't that necessary in a communication server.
I just think that Red5 should be a very approachable server, the key to that is the core API so keeping as near as possible to the standard Macromedia API's in order to attract Flash Coders and Designers. I think all the other functionality everyone's spoken about could then be best achieved by making the server extensible via plug ins with a flash-esque API that can be consumed natively within any Red5 flash comm. Script. Then, for the super doper clever stuff that any Java coder wants to add on it's up to them to get stuck in and mod Red5 as they see fit, it is after all open source.
Hope I've not put noses out of joint?
Regards
Justin.
_______________________________________________
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
