Changes between Version 3 and Version 4 of Ticket #999


Ignore:
Timestamp:
2010-03-31T16:50:14Z (15 years ago)
Author:
davidsarah
Comment:

fix typo

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #999 – Description

    v3 v4  
    11(originally I incorrectly posted this to #917)
    22
    3 The way to do it is to make a variant of [source:src/allmydata/storage/server.py] which doesn't read from local disk in its [source:src/allmydata/storage/server.py@4164#L359 _iter_share_files()], but instead reads the files using its backend protocol, e.g. from its S3 bucket (it is an S3 client and a Tahoe-LAFS storage server). Likewise variants of [source:src/allmydata/storage/shares.py@3762 storage/shares.py], [source:src/allmydata/storage/immutable.py@3871#L39 storage/immutable.py], and [source:src/allmydata/storage/mutable.py@3815#L34 storage/mutable.py] which write their data out using the backend protocool instead of to their local filesystem.
     3The way to do it is to make a variant of [source:src/allmydata/storage/server.py] which doesn't read from local disk in its [source:src/allmydata/storage/server.py@4164#L359 _iter_share_files()], but instead reads the files using its backend protocol, e.g. from its S3 bucket (it is an S3 client and a Tahoe-LAFS storage server). Likewise variants of [source:src/allmydata/storage/shares.py@3762 storage/shares.py], [source:src/allmydata/storage/immutable.py@3871#L39 storage/immutable.py], and [source:src/allmydata/storage/mutable.py@3815#L34 storage/mutable.py] which write their data out using the backend protocol, instead of to their local filesystem.
    44
    55Probably one should first start by abstracting out just the "does this go to local disk, S3, Rackspace Cloudfiles, etc" part from all the other functionality in those four files...  :-)