[Bug 756000] gstrtmpsink: add unlock

[GStreamer (GNOME Bugzilla)]

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

--- Comment #12 from Tim-Philipp Müller <t.i.m at zen.co.uk> ---
> > Another issue is more conceptual: it seems to me that the assumption here is
> > that unlock=shutdown, but theoretically it could have been triggered by a
> > flushing seek for example - would one want to re-connect in that case?
> 
> That could simply be fixed by reconnecting in unlock_stop() I believe. 

But then it's not a continuous stream any more, which is what my question boils
down to really. unlock_stop() isn't really supposed to interfere with that (but
I could live with this in this context).

> There is no way to unlock network operations without having to
> reset the connection. That is true for many protocols.

I don't entirely understand this comment, could you elaborate what you mean?
Are you talking about the TCP protocol level or some other protocol? Isn't this
mostly an implementation detail? The rtmp implementation could surely be done
in a way that's always fully async and fully interruptible (worst case you
leave behind a thread that's stuck in some non-async connect or dns lookup,
no?)?

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