[tahoe-lafs-trac-stream] [tahoe-lafs] #1111: PyFilesystem backend

[tahoe-lafs]

#1111: PyFilesystem backend
-----------------------------+----------------------------------------------
     Reporter:  zooko        |       Owner:  slush                             
         Type:  enhancement  |      Status:  reopened                          
     Priority:  major        |   Milestone:  soon                              
    Component:  contrib      |     Version:  1.7.0                             
   Resolution:               |    Keywords:  pyfilesystem fuse test-needed docs
Launchpad Bug:               |  
-----------------------------+----------------------------------------------

Comment (by davidsarah):

 Replying to [comment:9 slush]:
 > If PyFS need some help, it is better RemoteFileBuffer, which manage
 loading and storing files to remote filesystems (in general, not only
 TahoeLAFS). Opening large remotte files directly from applications (movie)
 is still with troubles, because seeking in remote file needs loading full
 content before. I have improvements of this in my head, but time is my
 problem now.

 (!RemoteFileBuffer source is
 [https://code.google.com/p/pyfilesystem/source/browse/trunk/fs/remote.py?spec=svn620&r=620#46
 here].)

 The SFTP frontend has [source:src/allmydata/frontends/sftpd.py at 4545#L290
 OverwriteableFileConsumer] which is doing essentially the same thing. Like
 !RemoteFileBuffer, reading a chunk waits until all of the data up to the
 end of that chunk has been downloaded; segments are never downloaded out-
 of-order. Unlike !RemoteFileBuffer, it supports writing chunks of the file
 that haven't been read yet.

 Out-of-order downloads would require use of HTTP range requests, if the
 connection to the web-API gateway is over HTTP.

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