Re: Where is libgvfsdbus.so loaded?

[Jean-Philippe Green <jeanphilippe green gmail com>]

Ok, thanks. It sounded like loading libgvfsdbus.so would extend GIO, but it's actually kind of the other way around, right?

I still don't really understand how GIO knows what library to use when extended. And where in the code does it figure out that it needs to be extended? Does GIO knows what protocols are supported by GVfs or is it up to the GVfs library to tell GIO what it supports once it has been extended?

I'm sorry for asking many dumb questions, but I can't get this straight in my head.

2013/5/29 Bastien Nocera <hadess hadess net>

On Thu, 2013-05-23 at 15:54 +0200, Jean-Philippe Green wrote:
> Hey!
>
> The documentation (https://live.gnome.org/gvfs/doc) says that the
> master gvfs daemon is "Initialized on the client side again as an
> extension point by loading the libgvfsdbus.so library". My question
> is, where is libgvfsdbus.so loaded? I have used grep to find out where
> it is used in the source code of glib (including gio and gobject),

It's loaded in GIO, as an extension point (ie. you won't find that exact
string in the sources).

>  gtk, gedit and nautilus, but it doesn't seem to be loaded anywhere.
> What part of GNOME loads gvfs when needed?
>
> If by client side, you mean the client libraries that resides in the
> client directory of gvfs, then what parts of GNOME loads those parts?
> Is it up to the applications themselves or a library such as glib?