summaryrefslogtreecommitdiff
path: root/daemon/gvfsbackendmtp.h
diff options
context:
space:
mode:
authorPhilip Langdale <philipl@overt.org>2013-02-24 15:42:02 -0800
committerPhilip Langdale <philipl@overt.org>2013-03-30 16:25:13 -0700
commit79f94867d39bab750fb437ffe552f943cfda0add (patch)
treee0fee467fc4b7062aa37c2a3f0c6d665e71b7563 /daemon/gvfsbackendmtp.h
parente88aa8dad358a23c164a95267f7dd8415d377b21 (diff)
downloadgvfs-79f94867d39bab750fb437ffe552f943cfda0add.tar.gz
MTP: Use normal filenames in paths.
It's becoming too fragile to use item IDs as path elements. Beyond the problems with clients that don't use copy names, there are a bunch of situtations where a path sent by a client could be an id or a filename and it's not 100% possible to tell them apart. When the initial feature set of very limited, this wasn't much of an issue, but with direct read/write support, we are now exposed to a huge set of clients (as opposed to just file managers) with no ability to recognise copy names, and which generate a lot of mixed form paths, so we're past the tipping point where it's now less of a hassle to maintain a name to id mapping. https://bugzilla.gnome.org/show_bug.cgi?id=696016
Diffstat (limited to 'daemon/gvfsbackendmtp.h')
-rw-r--r--daemon/gvfsbackendmtp.h2
1 files changed, 2 insertions, 0 deletions
diff --git a/daemon/gvfsbackendmtp.h b/daemon/gvfsbackendmtp.h
index 0fe1decb..d7a7fe3c 100644
--- a/daemon/gvfsbackendmtp.h
+++ b/daemon/gvfsbackendmtp.h
@@ -54,6 +54,8 @@ struct _GVfsBackendMtp
LIBMTP_mtpdevice_t *device;
char *dev_path;
+ GHashTable *file_cache;
+
GHashTable *monitors;
guint hb_id;
gint unmount_started;