[gstreamer-bugs] [Bug 309117] [filesink] non-fatal out of disk space handling

GStreamer (bugzilla.gnome.org) bugzilla-daemon at bugzilla.gnome.org
Wed Feb 6 03:22:03 PST 2008


If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=309117

  GStreamer | gstreamer (core) | Ver: HEAD CVS

Tim-Philipp Müller changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
 Attachment #104545|none                        |reviewed
               Flag|                            |




------- Comment #8 from Tim-Philipp Müller  2008-02-06 11:22 UTC -------
IMHO this is a bit awkward API-wise. We should avoid signals from the streaming
thread wherever possible, even more so complicated things where the app has to
handle blocking in the callback.

Couldn't we just post an element message of some sorts on the bus (if
requested, e.g. via setting a property) and block the writing thread on a cond
and then have the app do something (e.g. via g_signal_emit (sink,
"continue-writing", ..) or an interface+method) to make the writing thread
unblock and retry? Not quite as elegant as the signal since the app would
actively need to tell us that it wants the new behaviour, but easier for apps
to implement.


-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=309117.




More information about the Gstreamer-bugs mailing list