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

[GStreamer (bugzilla.gnome.org)]

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




------- Comment #40 from René Stadler  2009-03-11 22:57 UTC -------
(In reply to comment #39)
> Also GIO needs to support non-default main contexts for it's async operations
> before we can use them. Until then it's only as good as gnomevfs in this regard
> (you can cancel sync operations from other threads).
> 
> The authentication problem is, that we a) can't do authentication inside the
> plugin because it also runs on the default main context and b) we need to tell
> the application about the authentication issue, the application then has to
> show a dialog, mount the filesystem and then tell the plugin that everything is
> good now.
> 

And that's the problem -- you can't interact with the user to get the
authentication during a state change. That is why it's OK that Alex closed my
feature request for mainloop-less async mount operation as WONTFIX. It's either
sync or you error out anyways: The app needs to gio-mount any location itself
before setting the state. This is only a regression if you consider the old
gnomevfs elements' solution as working, which I don't. It was just a giant hack
IMO...

It should still be possible to make the gio elements attempt to mount
theirselves, but it's impossible to provide credentials so this would only fix
password-less locations (good enough for gst-launch and lazy apps though).


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