[gstreamer-bugs] [Bug 338827] [patch] gnomevfssrc should use async api to not block on network problems

GStreamer (bugzilla.gnome.org) bugzilla-daemon at bugzilla.gnome.org
Wed Mar 11 03:02:21 PDT 2009


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=338827

  GStreamer | gst-plugins-base | Ver: git

Tim-Philipp Müller changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |t.i.m at zen.co.uk




------- Comment #37 from Tim-Philipp Müller  2009-03-11 10:03 UTC -------
> Wouter, Stefan : *IF* this bug is still valid, there's a better alternative to
> fixing this issue, by not doing the connection in NULL=>READY
> (GstBaseSrc.start()) but in READY=>PAUSED (.render()).
> 
> This should be done for all sources for which we can't guarantee an immediate
> response (anything 'potentially' involving network).

This only hides the problem, it doesn't fix it at all. You might still get
blocking when shutting down if you do this (e.g. when user starts playing
something, then hits the next button).

Having said that, I think we should just declare gnomevfs* stuff as WONTFIX and
deprecate the gnomevfs elements and remove the experimental status from the gio
elements.


-- 
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=338827.




More information about the Gstreamer-bugs mailing list