Hello Stanislaw, sounds like the problem I had before as well. I solved it for me by forcing Red5 to use AMF3 in server code.
I also created a ticket for that issue in JIRA: http://jira.red5.org/browse/APPSERVER-188 The ticket also describes my very minor changes to the server code. Hope this helps until the issue is solved... Dominik > Date: Tue, 28 Aug 2007 23:22:21 +0200 > From: "Stanislaw Fiedor" <[EMAIL PROTECTED]> > Subject: [Red5] Problems with AMF3 types in RED5 (ByteArray) > To: <[email protected]> > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; format=flowed; charset="iso-8859-1"; > reply-type=original > > Hello, > I'm working right now with ByteArrays and I've got some problems: > - When sending an ByteArray to RED5 I get a decoding error on RED5 > - When sending an ByteArray from RED5 to my Flex client I'm getting an : > Type Coercion failed: cannot convert [EMAIL PROTECTED] to > flash.utils.ByteArray. > which means that I get an Array of Arrays with Numbers and NOT an ByteArray > Therefore I'm assuming that RED5 uses the AMF0 and not AMF3 - please > compare: > http://livedocs.adobe.com/flex/2/fds2javadoc/flex/messaging/io/amf/ActionMessageInput.html > and > http://livedocs.adobe.com/flex/2/fds2javadoc/flex/messaging/io/amf/ActionMessageOutput.html > > So my question is: Is there a setting for choosing AMF type on the server > side? Cause my clientside objectencoding is AMF3 and everything should be > ok.. > > Anybody else experienced problems with ByteArrays? > I will be glad for any help or suggestions. > BR > stf > _______________________________________________ Red5 mailing list [email protected] http://osflash.org/mailman/listinfo/red5_osflash.org
