Closed GoogleCodeExporter closed 9 years ago
Original comment by mondain
on 15 Nov 2011 at 3:33
After making the local fix to use AMF0/ AMF3 based on the encoding set by
client, the Shared Object always write AMF0 header even if flash client uses
AMF3. Since Red5 writes AMF0, the flash client simply reject the attribute
changes made by Red5.
The main aim of raising this defect is to fix the ByteArray send/receive by
both RTMPClient and Flash Client.
Original comment by bhagwat....@gmail.com
on 16 Nov 2011 at 2:06
I'm seeing the same error on Red5 1.0 and Windows 2008 Server.
Original comment by Ste...@Velocedge.com
on 16 Nov 2011 at 6:20
I've made a few changes to how this is handled across the board so please
retest with at least revision 4300 and let me know how it goes.
Original comment by mondain
on 1 Dec 2011 at 9:39
Hi,
I will do the re-test over this weekend and also make the sample Project in
Red5, Flash and Java to do the re-test if required in future.
Original comment by bhagwat....@gmail.com
on 9 Dec 2011 at 3:54
Shared object issues appear to be resolved starting with revision 4304.
Original comment by mondain
on 9 Dec 2011 at 10:31
Original issue reported on code.google.com by
bhagwat....@gmail.com
on 4 Oct 2011 at 10:48