fuse desktop integration / management library

Kevin Krammer kevin.krammer at gmx.at
Tue Apr 24 12:31:42 PDT 2007

On Freitag, 20. April 2007 +0100, nf2 wrote:


> the fuse management system should consist of three parts:
> * a glib main-loop based client library (async mount/umount operations,
> events)
> * a dbus service (session bus)
> * an (optionally linked) library used in fuse modules for authentication
> callbacks and progress/logging events

Designing a good library is quite hard, maybe it would be easier, especially 
to get something usable fast, to just implement the management service and 
decide later if it is necessary to split something into a reusable library.

My guess is that there won't be much need for alternative daemon 
implementations if the original one is already good, so any effortspent for 
clean library design would be "wasted" if there will always be jsut the 
original daemon using it.

On the subject of progress, I think there is an ongoing collaboration of GNOME 
and KDE developers to create a D-Bus interface specification for this.

> i am working on a desktop independent vfs library
> (http://www.scheinwelt.at/~norbertf/devel/vio/), but perhaps FUSE should
> also be considered as an option to get the "layering" right - to move
> VFS related stuff underneath the desktop layer...

The problem of using "local file access" from GUI applications is that there 
needs to be mechanisms to ensure they can list directories and read/write 
files without blocking. They need to have a way to discover that a file is 
actually a remote resource.


Kevin Krammer, KDE developer, xdg-utils developer
KDE user support, developer mentoring
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.freedesktop.org/archives/xdg/attachments/20070424/76acfa94/attachment.pgp 

More information about the xdg mailing list