After receiving the "set chunk size" message from the server, php-rtmp-client
starts using this size for both ingoing (server->client) and outgoing
(client->server) communications. However, use of a non-default (i.e. != 128)
client->server size should be properly notified to the server with an
appropriate control message. Failure to do so results in mysterious server
errors and/or timeouts, as I happened to discover with FMS 4.
If we want to keep things simple (i.e. keep using the 128-byte default for
encoding client->server messages), we have to use two variables (in place of
the single $chunkSize in RtmpClient.class.php) to independently store ingoing
and outgoing chunk sizes.
I'm attaching a patch with my fix.
Original issue reported on code.google.com by santi...@gmail.com on 25 Oct 2010 at 1:47
Original issue reported on code.google.com by
santi...@gmail.com
on 25 Oct 2010 at 1:47Attachments: