When I hear Mike Chambers say things like that, I immediately think he knows something ;)  Case in point - when I had told a user some time ago that "Normal mode" was gone forever, Mike corrected me and said "never say never..." - then bam, here's normal mode back in F8!

With that said, I feel like I should weigh in with what Red5's done.  We've sniffed packets and reconstructed the RTMP protocol (if you've been on the email list, you've seen all of this).  No decompilation of ANY executables has EVER been done - nor will it EVER be by the Red5 group.  Everything else has been constructed on other completely open source projects (Spring, MINA) - which everyone has been able to see since day 1.  I guess the real question is:  Is there a problem with HOW we deliver an already open AMF packet to an already free client with an open standard file format?  I'm not saying that there is or is not an issue or anything, I'm just simply posing the question. 

Our goal would be to be embraced by MM and that we'd have a good relationship.  Frankly, I'd hope we too could fill a void like openAMF and the others.  In fact, I really think it's tremendous boost in the arm for MM to have Red5 around.  The clients that can afford FCS will continue to use it because MM's name is behind it for support, and the users that could never afford it could actually begin to get a taste for it with the possibility of moving up to FCS projects someday.  But more than that, this technology could really enhance the lives of non-profit, educational and medical groups and certainly widen the developer community for FCS applications etc.

Anyway, I just wanted to be clear, that we've been above and beyond with what and how we're doing Red5.

Thanks all,

On 10/25/05, Mark Winterhalder <[EMAIL PROTECTED]> wrote:
> Secondly, it
> was always an issue before the arrival of MTASC

Oh, you read slashdot, too? :)

mark


On 10/26/05, The Irrelevant Elephant <[EMAIL PROTECTED] > wrote:
> Patrick Mineault wrote:
> > Well as far as amfphp is concerned I believe from contacts with MM that
> > they have given us implicit consent as they have mentionned that
> > Remoting will not be made available for PHP by MM itself but they are
> > aware that the need is there, so we're just filling a void.
>
> Although probably far too premature for discussion, an open source AS3
> compiler would also fill a small void.  I think Macromedia can rest
> assured that the chances of the open source community seriously
> rivalling Flex are pretty much zero, and for the most part people will
> buy Flex for the entire platform - not just the compiler, and not just
> for access to the 8.5 player.  An open source compiler opens up options
> for those developers who do not wish to use the Flex platform - which is
> by no means applicable in every situation.
>
> Of course, in future the Flash IDE will support Flash 8.5 - but even so,
> will it feature a command line compiler?  Who knows...  If it will, then
> maybe there is less of a requirement for an open source compiler - since
> I suspect for the most part everyone will at least have the Flash IDE.
>
> > We still have 6 months until FP8.5 and the bytecode is not even stable
> > yet so it's a stale discussion anyways, as an attempt at that would be
> > pretty useless. I suggest the 'shut up and wait' approach. Personally I
> > don't mind paying a grand for a compiler, but I do understand people
> > (say Claus) have issues with it, especially if they are developing
> > non-commercial products. But then again that's always been an issue
> > before the arrival of MTASC on the scene.
>
> True to some extent, however missing a couple of vital details.
> Firstly, it's kinda fun.  That gives us 6 months to play around when we
> feel like it, no pressure to actually produce anything.  Secondly, it
> was always an issue before the arrival of MTASC - true, but the
> departure of MTASC (from Macromedia compatibility) means that this hole
> is ready to open up again when everybody wants to target 8.5.
>
> "Shut up and wait" is all well and good, but it's not really much fun ;-)
>
> _______________________________________________
> osflash mailing list
> [email protected]
> http://osflash.org/mailman/listinfo/osflash_osflash.org
>


--
http://snafoo.org/
jabber: [EMAIL PROTECTED]

_______________________________________________
osflash mailing list
[email protected]
http://osflash.org/mailman/listinfo/osflash_osflash.org



--
John Grden - Blitz
_______________________________________________
osflash mailing list
[email protected]
http://osflash.org/mailman/listinfo/osflash_osflash.org

Reply via email to