[Bug 571722] shout2send: use nonblocking network I/O

[GStreamer (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=571722

Tim-Philipp Müller <t.i.m at zen.co.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|[shout2send] use            |shout2send: use nonblocking
                   |nonblocking network I/O     |network I/O

--- Comment #11 from Tim-Philipp Müller <t.i.m at zen.co.uk> ---
The 30s connect timeout should probably be a separate property.

What I don't think is right is to treat the internal queue building up as a
fatal error, it could happen when there's a transient network problem, in which
case we don't want to error out, or if bandwidth is too low. This makes things
more brittle than robust IMHO, at least if I understand the patch correctly.

I think there should be a time-based timeout that is reset whenever we
successfully send more data, or was there a reason that can't be done?

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.