Re: [Red5] Mission Creep?

[a /]

Indeed. It will allow for true client/server pattern based development. At the moment all we can do is create a client developed on a design pattern, then plug it to the server   [a /]   From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jake Hilton Sent: 11 April 2006 16:46 To: Red5@osflash.org Subject: Re: [Red5] Mission Creep?   I agree Ayo... one huge advantage already is true oop on the server. With java capabilities it really strengthens red5's stance... Makes it more like an application/streaming server rather than just a streaming server. Jake On 4/11/06, Lee McColl-Sylvester <[EMAIL PROTECTED]> wrote: Nicely said!   I once built a product for the purpose of selling, but had it quoted from a friend that he only opted for open source technologies, so didn't want to use it (even though I offered it for free).  Thing is, everything he built, he sold!   Lee     From: [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED]] On Behalf Of a / Sent: 11 April 2006 16:28 To: Red5@osflash.org Subject: Re: [Red5] Mission Creep?   I see R5 as a much needed option to FMS, capable of performing and hopefully outstripping the capabilities of FMS. By its very nature of being open source, it means that development will not be totally governed by economics but more from a developer point of view. In some respect it will also drive improvements in FMS development. Every Coca Cola needs a Pepsi. [a /]   From: [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED]] On Behalf Of John Grden Sent: 11 April 2006 15:39 To: Red5@osflash.org Subject: Re: [Red5] Mission Creep?   Thanks Rob, and not to rain on what you've said here, I think it's appropriate to point out that we (Red5 team) don't look at Red5 as being a replacement for FCS by any means.  It's a much needed option and I think a tremendous boost for Flashers everywhere. I'm not trying to make an example out of you Rob, so please don't take it that way ;)  I just see alot of posts saying it's a replacement and I wanted to point out that we don't view it that way.  Everyone I think can recognize that some companies/projects will only work with a product that has a company who can support it with a support contract etc and vise-versa - some will only work with OS or similar open formats.  And obviously, there's a ton of projects that are educational/non-profit/medical that maybe Red5 can help out with. Anyway, \m/ On 4/11/06, Rob Terrell < [EMAIL PROTECTED]> wrote: Justin, I'm following the Red5 developer list, and I don't get the sense that there is any mission creep happening at all. Quite a bit of what gets discussed on this list is off-topic -- not to willfully divert the developers, but out genuine excitement. Some (including myself) have discussed topics like transcoding, porting to C or C#, server-side Ruby, and other things. But that's talk over here -- not on the dev list.    The devs are plugging away, following the roadmap (if you haven't seen it, take a look at it). The progress they're making is right towards what you're looking for -- a feature-complete replacement for FCS. As for a cleaned-up API that looks similar to the FCS API, you should see what you're looking for in the .6 release. .4 is the release being worked on now. And if you're not afraid to roll up your sleeves and port your server-side actionscript code to Java, you can do quite a bit with Red5 today.   Today you can connect a NetConnection, make a NetStream, and play live or archived video. You can send arbitrary messages on that net connection. You can create persistent shared objects. A lot of stuff people want to implement ( i.e. video chat rooms) is possible today.      On Apr 11, 2006, at 9:58 AM, Justin Lewis wrote:   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 Red5@osflash.org http://osflash.org/mailman/listinfo/red5_osflash.org   _______________________________________________ Red5 mailing list Red5@osflash.org http://osflash.org/mailman/listinfo/red5_osflash.org -- John Grden - Blitz _______________________________________________ Red5 mailing list Red5@osflash.org http://osflash.org/mailman/listinfo/red5_osflash.org

_______________________________________________
Red5 mailing list
Red5@osflash.org
http://osflash.org/mailman/listinfo/red5_osflash.org