Changes between Initial Version and Version 1 of Ticket #1111, comment 10
- Timestamp:
- 2011-01-29T00:40:13Z (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #1111, comment 10
initial v1 4 4 (!RemoteFileBuffer source is [https://code.google.com/p/pyfilesystem/source/browse/trunk/fs/remote.py?spec=svn620&r=620#46 here].) 5 5 6 The SFTP frontend has [source:src/allmydata/frontends/sftpd.py@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.6 The SFTP frontend has [source:src/allmydata/frontends/sftpd.py@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~~ downloaded yet. 7 7 8 8 Out-of-order downloads would require use of HTTP range requests, if the connection to the web-API gateway is over HTTP.