> 03 00 00 00 00 01 22 14 00 00 00 00 02 00 07 63 
> 6f 6e 6e 65 63 74 

> 00 
This is to indicate we have a double (8 bytes)

> 3f f0 00 00 00 00 00 00 
This is a double in network byte order

> 03 
This is to indicate we have an object

> 00 03 
Length of the object variable in network byte order (3 bytes)

> 61 70 70 
The actual string (variable)

etc.. etc..

Yours, Sander


---------- Original Message ----------------------------------
From: p_j_r_m <[EMAIL PROTECTED]>
Reply-To: Open Source Flash Mailing List <[email protected]>
Date:  Thu, 17 Jan 2008 12:46:05 -0800 (PST)

>Hi all:
> 
> I'm trying to understand the AMF/RTMP calls made to a red5 or haxeVideo 
> servers in order to stablish a session.
> After the handshakes I have seen this bytes with ethereal (Connect call) :
> 
> 03 00 00 00 00 01 22 14 00 00 00 00 02 00 07 63 
> 6f 6e 6e 65 63 74 00 3f f0 00 00 00 00 00 00 03 
> 00 03 61 70 70 02 00 00 00 08 66 6c 61 73 68 56 
> 65 72 02 00 0c 4c 4e 58 20 39 2c 30 2c 34 38 2c 
>  
> (In text this is                                           
>  ......"........connect.?ð.........app.....flashVer...LNX 
> 9,0,48,0..swfUrl..1file:///root/HAXE/HX
> )
> 
> Ok. I think the first 12 bytes are the RTMP header, then a 02 marks an AMF 
> String object with size 0007, which is the "connect". But  then I see 
> 
> 3f f0 00 00 00 00 00 00 
> 
> and
> 
> 03 00 03 
> 
> until the "app" string.
>Could you explain the meaning of this bytes?  I am intrigued specially about 
>that 3f f0 bytes. I have read the RTMP draft document at this site, but I 
>don't see how this matches with that.
> 
> Thank you very much
> 
> 
>   
>       
>---------------------------------
>Looking for last minute shopping deals?  Find them fast with Yahoo! Search.
>
>
>
 




________________________________________________________________
Sent via the WebMail system at wichers.nu


 
                   


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

Reply via email to