Hello Dominik,

thanks for your response;)

I hoped that what you have written is gonna help me.. but unfortunately I 
guess that it won't.
When sending a ByteArray to RED5 I get a:

[INFO] 2007-08-29 17:46:49,125 SocketAcceptorIoProcessor-0.0:( 
org.red5.io.amf3.Input.readDataType ) Unknown datatype: 12

so as you can see it uses the correct amf version but it can't find the 12 
datatype.. - take a look at the org.red5.io.amf3;  Class.

It seems that there is NO handling for this type of a data:


/**

* Object start marker

*/

public static final byte TYPE_OBJECT = 0x0A;


/**

* XML start marker

*/

public static final byte TYPE_XML = 0x0B;


//public final static byte TYPE_YYY = 0x0C; 
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

//public final static byte TYPE_ZZZ = 0x0D; 
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!



So

Therefore I guess that first of all the ByteArray type needs to be 
implemented into the AMF3 Class to get it working.. unfortunately I'm rather 
a java newbie therefore I hope that some RED5 DEV's will  be able to add it.

stf


----- Original Message ----- 
From: "Dominik Willers" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Wednesday, August 29, 2007 11:54 AM
Subject: Re: [Red5] Problems with AMF3 types in RED5 (ByteArray)


> 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
> 


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

Reply via email to