RTMP handshake compliance for clients
authorKevin DuBois <kdub432@gmail.com>
Wed, 8 Jul 2009 07:19:38 +0000 (09:19 +0200)
committerRémi Duraffort <ivoire@videolan.org>
Wed, 8 Jul 2009 07:19:38 +0000 (09:19 +0200)
commitaf0ba1445194d0251a6e8a0811cb15e83e6ef99e
treefe00c6ffac0e665c220d78c02d3e6628db8e2c65
parent3b03fae9160b840995804c713db79740d202a62f
RTMP handshake compliance for clients

The spec says that the 2nd round of packets need to have the 1st 4 bytes be the
timestamp (potentially zero) and the next 4 bytes be zero. The bytes after that
should be random. (not necessarily cryptographically secure, just for
establishing a unique echo response in the 3rd round of packets).

Signed-off-by: Rémi Duraffort <ivoire@videolan.org>
modules/access/rtmp/rtmp_amf_flv.c