author | Ognyan Tonchev <ognyan@axis.com> | |
Mon, 30 Jan 2012 14:55:26 +0000 (15:55 +0100) | ||
committer | Tim-Philipp Müller <tim.muller@collabora.co.uk> | |
Fri, 17 Feb 2012 14:49:52 +0000 (14:49 +0000) | ||
commit | 07aa26a2c3c168f35ed3ed2c5c0702f460c8cf86 | |
tree | 9f8c49f75d204cdd3595e0740da457ee2a146543 | tree | snapshot (tar.xz tar.gz zip) |
parent | fd58cc5e542be90156e60f4760281fa0313babd3 | commit | diff |
rtspconnection: only send new data immediately if there are no queued messages
Even if watch->messages->length is 0 there may still be some
data from a message that was only written partially at the
previous attempt stored in watch->write_data, so check for
that as well. We don't want to write data into the middle
of another message, which could happen when there wasn't
enough bandwidth.
https://bugzilla.gnome.org/show_bug.cgi?id=669039
Even if watch->messages->length is 0 there may still be some
data from a message that was only written partially at the
previous attempt stored in watch->write_data, so check for
that as well. We don't want to write data into the middle
of another message, which could happen when there wasn't
enough bandwidth.
https://bugzilla.gnome.org/show_bug.cgi?id=669039
gst-libs/gst/rtsp/gstrtspconnection.c | diff | blob | history |