[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):

 I'm confused about leases. When I look at the constructor for an immutable
 share file in a 'pristine' repository, (or in my latest version for that
 matter) I see that in the "create" clause of the constructor a python
 string representation of a big endian '0' is used for the number of
 leases.

 http://tahoe-lafs.org/trac/tahoe-
 lafs/browser/trunk/src/allmydata/storage/immutable.py#L63


 This is confusing because in my test vector data (created some time ago) I
 have '1' as the initial number of leases.  My guess is that I somehow got
 a bum test-vector value, but it'd be nice to hear from an architect that
 immutable share files really should start life with '0' leases!

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