[tahoe-lafs-trac-stream] [tahoe-lafs] #1429: automatically upload a file when it is put in a given local directory

[tahoe-lafs]

#1429: automatically upload a file when it is put in a given local directory
-------------------------+-------------------------------------------------
     Reporter:           |      Owner:
  davidsarah             |     Status:  new
         Type:           |  Milestone:  1.9.0
  enhancement            |    Version:  1.8.2
     Priority:  major    |   Keywords:  drop-upload inotify usability
    Component:  code-    |  review-needed
  frontend               |
   Resolution:           |
Launchpad Bug:           |
-------------------------+-------------------------------------------------

Comment (by davidsarah):

 Replying to [comment:10 warner]:
 > This is pretty cool stuff. I'm hesitant about landing it in Tahoe core,
 though.. at least in its present form, it feels more like something that
 wants to be in a plugin, or in an extensions/ sort of directory.

 We don't have a plugin mechanism. In any case, I'm not encouraged by the
 fate of things that were previously out-of-core, like the FUSE
 implementations. I'd prefer it to be in the core, tested by default, and
 available for all users to try out without installing anything else.

 If it introduced ''new'' dependencies that would be a different matter,
 but it doesn't (and we'd decided that it was OK to depend on Twisted 10.1,
 which has other advantages).

 > If it were a more complete Dropbox-ish replacment, I'd feel better about
 it: watching all directories under a root, handling modification of
 existing files not just new ones, and ideally some kind of multiple-client
 support. (as is, it's more like an automatic backup tool than a sync-a
 -virtual-directory-across-multiple-machines tool).

 I didn't intend it to be a sync-a-virtual-directory-across-multiple-
 machines tool. It just uploads things that you drop into a particular
 directory. Perhaps the name 'drop-upload' suggests that it is more similar
 to Dropbox than it is. We have time before the 1.9 release to rename it,
 if a better name is suggested.

 It already handles modification of existing files (I'll add that to the
 tests). Watching all directories under a root is #1433, and is a
 relatively straightforward evolution of the current code.

 > Can you envision maintaining its current UI for a couple years?

 Yes, absolutely. It'll be easy to maintain compatibility with the current
 UI, that's only a few lines of code and documentation. It also needs to be
 in core to get sufficient feedback on the UI to improve it.

-- 
Ticket URL: <http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1429#comment:11>
tahoe-lafs <http://tahoe-lafs.org>
secure decentralized storage