[tahoe-dev] Public web interface

[Greg Troxel]

I see the whole approach to "dropbox like functionality" and "web
server" as basically broken, and coming from a world view where
tahoe-lafs is the primary thing, rather than viewing it as one of many
filesystems (albeit with different, interesting and useful properties
than many).   So I think that option 2 is right.

For "dropbox-like functionality", I'd like to see that be something that
can work between two places in the filesystem, of which one of them
could be tahoe.  I don't see any reason this should be bound to tahoe
specifically.

My point is basically to consider what happened if every filesystem took
this view, and there were N implementations of syncing and web servers.
Does that really make sense?  I don't think tahoe is *that* special.

  Greg
  resident VFS crank

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 194 bytes
Desc: not available
URL: <http://tahoe-lafs.org/pipermail/tahoe-dev/attachments/20121203/49c0e8ef/attachment.pgp>