Re: GVFS + LibreOffice + WebDAV
- From: Adam Tauno Williams <awilliam whitemice org>
- To: Andrew Beverley <andy andybev com>
- Cc: gvfs-list gnome org
- Subject: Re: GVFS + LibreOffice + WebDAV
- Date: Mon, 18 Mar 2013 09:29:54 -0400
On Thu, 2012-12-06 at 07:41 +0000, Andrew Beverley wrote:
On Wed, 2012-12-05 at 11:27 +0100, Alexander Larsson wrote:
Yes, gvfs doesn't really have any caching layer for files, although some
of the backends do have caches for directory and file metadata (like the
ftp backend). I've long wanted to implement a layer that implements
writing to files locally and flushing on close, as well as one for
reading where we start streaming to a local file as need but then read
from the local copy, allowing things like seeks to work.
There are some issues with these caches, for instance the fact that
close() is extremely expensive and is the only place that report real
i/o error is suprising to many apps, and will break things like progress
dialogs. Or we could fake the upload making close fast, but that risks
data loss due to undetected errors.
Also, there might be cases where you just want to stream an entire file
and it doesn't make sense to have a local copy. Maybe we could add some
flags that allow choosing what kind of behaviour you want.
Anyway, these things would be nice, but nobody is working on it atm.
I'd be keen to sponsor such development (cost dependent). Anybody
interested in carrying out the required work?
I'm going to take a look at working on GVFS; see if I can get my head
around it. I haven't worked in C in some some; mostly I work on Python
on the server side of the WebDAV connection.
But FreedomSponsors lets a bounty be posted and anybody work on it.
I'm not sure which is more pressing and grievous, this bug or
<https://bugzilla.gnome.org/show_bug.cgi?id=556749> [no caching of
PROPFIND results]; and perhaps some type of cache or at least tracking
mechanism would be required to support offline-write-save-at-end anyway.
Watching GVFS display a directory in an "OpenFiles" dialog and then
proceed to do a PROPFIND Depth 0 of ***EVERY OBJECT IN THE #&^#*#&
FOLDER*** is pretty aggravating [Dude, you already know all that!].
--
Adam Tauno Williams GPG D95ED383
Systems Administrator, Python Developer, LPI / NCLA
[
Date Prev][
Date Next] [
Thread Prev][Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]