[tahoe-lafs-trac-stream] [tahoe-lafs] #999: support multiple storage backends, including amazon s3

[tahoe-lafs]

#999: support multiple storage backends, including amazon s3
------------------------------+-----------------------------
     Reporter:  zooko         |      Owner:  Zancas
         Type:  enhancement   |     Status:  new
     Priority:  major         |  Milestone:  soon
    Component:  code-storage  |    Version:  1.6.0
   Resolution:                |   Keywords:  gsoc backend s3
Launchpad Bug:                |
------------------------------+-----------------------------

Comment (by Zancas):

 My current test suite contains several tests that Zooko calls "transparent
 box".  I need to decide whether they are appropriate.

  Test 1: remote_allocate_buckets populates incoming with shnum(s)
  Test 2: an attempt to allocate the same share (same ss) does _not_ create
 a new bucketwriter
  Test 3: test allocated size
  Test 4: together remote_write, remote_close, get_shares, and
 read_share_data behave

   Since I am altering the location (from server to backend/core) of some
 of this functionality, and since I am altering the mechanism by which the
 filesystem is manipulated (to FilePath)... I think all of these tests are
 necessary.

   It would be nice if the tests were designed to ensure the proper
 behavior independent of the underlying storage medium...  but I think I
 need to assume a filesystem-like interface for at least (1,2, and 4),
 probably (3) as well...

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