Re: Writing a gvfs backend

["Boyd Timothy" <btimothy gmail com>]

Any ETA on when you're planning to stabilize the DBus interface?
Ideally, it'd be nice if my already-running-process would just be able
to register a DBus interface name, and I could provide an xyz.mount
file that gvfs' daemon would just look and see the DBus interface
already registered in the session and could go about its own merry
way.  Thoughts/suggestions?

Thanks,

Boyd

On Sat, May 10, 2008 at 1:11 AM, Alexander Larsson <alexl redhat com> wrote:
> On Fri, 2008-05-09 at 11:29 -0600, Boyd Timothy wrote:
>> Hey Alex,
>>
>> I wondered if you could give me a couple pointers about writing a gvfs
>> backend.  I'd like to write one using something like python which only
>> exposes its interface via DBus.  Where can I look to see which
>> specific DBus Interfaces I need to implement, complete with their
>> method signatures?
>
> You can't do this at the moment. The dbus interfaces are not totally
> stable, and additionally file i/o is done using a custom binary protocol
> over a pipe. We have deliberately not stabilized either the dbus
> protocol or the daemon side C interface because we're still tweaking it
> as we learn how things work.
>
> The way you currently implement gvfs backends is by subclassing
> GVfsBackend and implement the operations there. I'd recommend you look
> at the current ones to see some examples.
>
>> Also, if I add a *.mount file to /usr/share/gvfs/mounts what (short of
>> rebooting) should I do to get gvfsd to pick that up?
>
> send usr1 to gvfsd, or restart gvfsd.
>
>
>