From hoisie at gmail.com Tue Aug 26 11:42:14 2008 From: hoisie at gmail.com (Michael Hoisie) Date: Tue, 26 Aug 2008 05:42:14 -0400 Subject: [rtmpy-dev] Connect fails with Flex SDK 3.1 Message-ID: <186dafe0808260242q78136513s99abdeebcc773c5@mail.gmail.com> Hi, I'm trying to get the latest version of Flex SDK (3.1) to connect to RTMPY, but the connection is closed by the client after the handshake. The client doens't like the Connect.succeeded message, and disconnects right after receiving it. I ran flash media server in parallel, and captured the those packets. There seem to be three more properties in fms' Connection.succeeded packet: fmsVer, capabilities, and objectEncoding. I tried adding these to RTMPy, but the result is not encoded properly (it doesn't obey the 128 byte boundaries). Has anyone tested RTMPy with flex 3? Thanks, Michael Hoisie http://hoisie.com/ (blog) P.S hex dump output: This is what RTMPy returns after connect: 0000: 02 00 07 5f 72 65 73 75 6c 74 00 3f f0 00 00 00 ..._result.?.... 0010: 00 00 00 05 03 00 04 63 6f 64 65 02 00 1d 4e 65 .......code...Ne 0020: 74 43 6f 6e 6e 65 63 74 69 6f 6e 2e 43 6f 6e 6e tConnection.Conn 0030: 65 63 74 2e 53 75 63 63 65 73 73 00 0b 64 65 73 ect.Success..des 0040: 63 72 69 70 74 69 6f 6e 02 00 15 43 6f 6e 6e 65 cription...Conne 0050: 63 74 69 6f 6e 20 73 75 63 63 65 65 64 65 64 2e ction.succeeded. 0060: 00 05 6c 65 76 65 6c 02 00 06 73 74 61 74 75 73 ..level...status 0070: 00 00 09 And this is what Flash Media Server 3 returns. It has a few more properties: fmsVer, capabilities, and objectEncoding: 0000 03 00 00 00 00 00 be 14 00 00 00 00 02 00 07 5f ..............._ 0010 72 65 73 75 6c 74 00 3f f0 00 00 00 00 00 00 03 result.?........ 0020 00 06 66 6d 73 56 65 72 02 00 0d 46 4d 53 2f 33 ..fmsVer...FMS/3 0030 2c 30 2c 31 2c 31 32 33 00 0c 63 61 70 61 62 69 ,0,1,123..capabi 0040 6c 69 74 69 65 73 00 40 3f 00 00 00 00 00 00 00 lities.@?....... 0050 00 09 03 00 05 6c 65 76 65 6c 02 00 06 73 74 61 .....level...sta 0060 74 75 73 00 04 63 6f 64 65 02 00 1d 4e 65 74 43 tus..code...NetC 0070 6f 6e 6e 65 63 74 69 6f 6e 2e 43 6f 6e 6e 65 63 onnection.Connec 0080 74 2e 53 75 63 63 65 73 73 00 0b 64 c3 65 73 63 t.Success..d.esc 0090 72 69 70 74 69 6f 6e 02 00 15 43 6f 6e 6e 65 63 ription...Connec 00a0 74 69 6f 6e 20 73 75 63 63 65 65 64 65 64 2e 00 tion succeeded.. 00b0 0e 6f 62 6a 65 63 74 45 6e 63 6f 64 69 6e 67 00 .objectEncoding. 00c0 40 08 00 00 00 00 00 00 00 00 09 @.......... From hoisie at gmail.com Wed Aug 27 02:53:57 2008 From: hoisie at gmail.com (Michael Hoisie) Date: Tue, 26 Aug 2008 20:53:57 -0400 Subject: [rtmpy-dev] Connect fails with Flex SDK 3.1 In-Reply-To: <186dafe0808260242q78136513s99abdeebcc773c5@mail.gmail.com> References: <186dafe0808260242q78136513s99abdeebcc773c5@mail.gmail.com> Message-ID: <186dafe0808261753x375b82d3p384aa24e71e76f38@mail.gmail.com> It seems like 'objectEncoding' was the missing piece. If you include that peroperty in the connect response, a netconnection will work in Flex Sdk 3.1: command.setResult(None, { 'level': 'status', 'code': 'NetConnection.Connect.Success', 'description': 'Connection succeeded.', 'objectEncoding':3 }) Haven't tested this with older versions of FMS, though. - Michael Hoisie http://hoisie.com/ (blog) On Tue, Aug 26, 2008 at 5:42 AM, Michael Hoisie wrote: > Hi, > I'm trying to get the latest version of Flex SDK (3.1) to connect to > RTMPY, but the connection is closed by the client after the handshake. > The client doens't like the Connect.succeeded message, and disconnects > right after receiving it. > > I ran flash media server in parallel, and captured the those packets. > There seem to be three more properties in fms' Connection.succeeded > packet: fmsVer, capabilities, and objectEncoding. I tried adding these > to RTMPy, but the result is not encoded properly (it doesn't obey the > 128 byte boundaries). > > Has anyone tested RTMPy with flex 3? > > Thanks, > Michael Hoisie > http://hoisie.com/ (blog) > > P.S hex dump output: > > This is what RTMPy returns after connect: > > 0000: 02 00 07 5f 72 65 73 75 6c 74 00 3f f0 00 00 00 ..._result.?.... > 0010: 00 00 00 05 03 00 04 63 6f 64 65 02 00 1d 4e 65 .......code...Ne > 0020: 74 43 6f 6e 6e 65 63 74 69 6f 6e 2e 43 6f 6e 6e tConnection.Conn > 0030: 65 63 74 2e 53 75 63 63 65 73 73 00 0b 64 65 73 ect.Success..des > 0040: 63 72 69 70 74 69 6f 6e 02 00 15 43 6f 6e 6e 65 cription...Conne > 0050: 63 74 69 6f 6e 20 73 75 63 63 65 65 64 65 64 2e ction.succeeded. > 0060: 00 05 6c 65 76 65 6c 02 00 06 73 74 61 74 75 73 ..level...status > 0070: 00 00 09 > > And this is what Flash Media Server 3 returns. It has a few more > properties: fmsVer, capabilities, and objectEncoding: > > 0000 03 00 00 00 00 00 be 14 00 00 00 00 02 00 07 5f ..............._ > 0010 72 65 73 75 6c 74 00 3f f0 00 00 00 00 00 00 03 result.?........ > 0020 00 06 66 6d 73 56 65 72 02 00 0d 46 4d 53 2f 33 ..fmsVer...FMS/3 > 0030 2c 30 2c 31 2c 31 32 33 00 0c 63 61 70 61 62 69 ,0,1,123..capabi > 0040 6c 69 74 69 65 73 00 40 3f 00 00 00 00 00 00 00 lities.@?....... > 0050 00 09 03 00 05 6c 65 76 65 6c 02 00 06 73 74 61 .....level...sta > 0060 74 75 73 00 04 63 6f 64 65 02 00 1d 4e 65 74 43 tus..code...NetC > 0070 6f 6e 6e 65 63 74 69 6f 6e 2e 43 6f 6e 6e 65 63 onnection.Connec > 0080 74 2e 53 75 63 63 65 73 73 00 0b 64 c3 65 73 63 t.Success..d.esc > 0090 72 69 70 74 69 6f 6e 02 00 15 43 6f 6e 6e 65 63 ription...Connec > 00a0 74 69 6f 6e 20 73 75 63 63 65 65 64 65 64 2e 00 tion succeeded.. > 00b0 0e 6f 62 6a 65 63 74 45 6e 63 6f 64 69 6e 67 00 .objectEncoding. > 00c0 40 08 00 00 00 00 00 00 00 00 09 @.......... > From lists at collab.nl Thu Aug 28 00:21:35 2008 From: lists at collab.nl (Thijs Triemstra | Collab) Date: Thu, 28 Aug 2008 00:21:35 +0200 Subject: [rtmpy-dev] Connect fails with Flex SDK 3.1 In-Reply-To: <186dafe0808261753x375b82d3p384aa24e71e76f38@mail.gmail.com> References: <186dafe0808260242q78136513s99abdeebcc773c5@mail.gmail.com> <186dafe0808261753x375b82d3p384aa24e71e76f38@mail.gmail.com> Message-ID: <61962B68-46A0-4A4E-8B7D-41072192A309@collab.nl> Hi Michael, RTMPy is unfortunately still a work in progress. We spent most of our time on PyAMF [1] during last months, but hopefully you will see activity in the RTMPy project again soon, especially now that there's a C extension for PyAMF in the making, which provides an even better solution for the AMF requirement in RTMPy. Hope that clears things up ;) Thijs [1] http://pyamf.org [2] http://pyamf.org/ticket/225 On 27 aug 2008, at 02:53, Michael Hoisie wrote: > It seems like 'objectEncoding' was the missing piece. If you include > that peroperty in the connect response, a netconnection will work in > Flex Sdk 3.1: > > command.setResult(None, { > 'level': 'status', > 'code': 'NetConnection.Connect.Success', > 'description': 'Connection succeeded.', > 'objectEncoding':3 > }) > > Haven't tested this with older versions of FMS, though. > > - Michael Hoisie > http://hoisie.com/ (blog) > > > > On Tue, Aug 26, 2008 at 5:42 AM, Michael Hoisie > wrote: >> Hi, >> I'm trying to get the latest version of Flex SDK (3.1) to connect to >> RTMPY, but the connection is closed by the client after the >> handshake. >> The client doens't like the Connect.succeeded message, and >> disconnects >> right after receiving it. >> >> I ran flash media server in parallel, and captured the those packets. >> There seem to be three more properties in fms' Connection.succeeded >> packet: fmsVer, capabilities, and objectEncoding. I tried adding >> these >> to RTMPy, but the result is not encoded properly (it doesn't obey the >> 128 byte boundaries). >> >> Has anyone tested RTMPy with flex 3? >> >> Thanks, >> Michael Hoisie >> http://hoisie.com/ (blog) >> >> P.S hex dump output: >> >> This is what RTMPy returns after connect: >> >> 0000: 02 00 07 5f 72 65 73 75 6c 74 00 3f f0 00 00 >> 00 ..._result.?.... >> 0010: 00 00 00 05 03 00 04 63 6f 64 65 02 00 1d 4e >> 65 .......code...Ne >> 0020: 74 43 6f 6e 6e 65 63 74 69 6f 6e 2e 43 6f 6e 6e >> tConnection.Conn >> 0030: 65 63 74 2e 53 75 63 63 65 73 73 00 0b 64 65 73 >> ect.Success..des >> 0040: 63 72 69 70 74 69 6f 6e 02 00 15 43 6f 6e 6e 65 >> cription...Conne >> 0050: 63 74 69 6f 6e 20 73 75 63 63 65 65 64 65 64 2e >> ction.succeeded. >> 0060: 00 05 6c 65 76 65 6c 02 00 06 73 74 61 74 75 >> 73 ..level...status >> 0070: 00 00 09 >> >> And this is what Flash Media Server 3 returns. It has a few more >> properties: fmsVer, capabilities, and objectEncoding: >> >> 0000 03 00 00 00 00 00 be 14 00 00 00 00 02 00 07 >> 5f ..............._ >> 0010 72 65 73 75 6c 74 00 3f f0 00 00 00 00 00 00 03 >> result.?........ >> 0020 00 06 66 6d 73 56 65 72 02 00 0d 46 4d 53 2f >> 33 ..fmsVer...FMS/3 >> 0030 2c 30 2c 31 2c 31 32 33 00 0c 63 61 70 61 62 69 , >> 0,1,123..capabi >> 0040 6c 69 74 69 65 73 00 40 3f 00 00 00 00 00 00 00 >> lities.@?....... >> 0050 00 09 03 00 05 6c 65 76 65 6c 02 00 06 73 74 >> 61 .....level...sta >> 0060 74 75 73 00 04 63 6f 64 65 02 00 1d 4e 65 74 43 >> tus..code...NetC >> 0070 6f 6e 6e 65 63 74 69 6f 6e 2e 43 6f 6e 6e 65 63 >> onnection.Connec >> 0080 74 2e 53 75 63 63 65 73 73 00 0b 64 c3 65 73 63 >> t.Success..d.esc >> 0090 72 69 70 74 69 6f 6e 02 00 15 43 6f 6e 6e 65 63 >> ription...Connec >> 00a0 74 69 6f 6e 20 73 75 63 63 65 65 64 65 64 2e 00 tion >> succeeded.. >> 00b0 0e 6f 62 6a 65 63 74 45 6e 63 6f 64 69 6e 67 >> 00 .objectEncoding. >> 00c0 40 08 00 00 00 00 00 00 00 00 09 @.......... >> > _______________________________________________ > RTMPy mailing list - rtmpy-dev at rtmpy.org > http://lists.rtmpy.org/mailman/listinfo/rtmpy-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.rtmpy.org/pipermail/rtmpy-dev/attachments/20080828/5a60dcb5/attachment.htm -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 194 bytes Desc: This is a digitally signed message part Url : http://lists.rtmpy.org/pipermail/rtmpy-dev/attachments/20080828/5a60dcb5/attachment.pgp