[tahoe-lafs-trac-stream] [tahoe-lafs] #1778: increase maximum mutable share size

[tahoe-lafs]

#1778: increase maximum mutable share size
------------------------------+-----------------------------------------
     Reporter:  davidsarah    |      Owner:  zooko
         Type:  defect        |     Status:  new
     Priority:  normal        |  Milestone:  1.9.2
    Component:  code-storage  |    Version:  1.9.1
   Resolution:                |   Keywords:  mutable large review-needed
Launchpad Bug:                |
------------------------------+-----------------------------------------
Changes (by zooko):

 * cc: warner (added)


Comment:

 Hm...
 {{{
         version = { "http://allmydata.org/tahoe/protocols/storage/v1" :
                     { "maximum-immutable-share-size": remaining_space,
                       "maximum-mutable-share-size":
 MAX_MUTABLE_SHARE_SIZE,
                       "tolerates-immutable-read-overrun": True,
                       "delete-mutable-shares-with-zero-length-writev":
 True,
                       "fills-holes-with-zero-bytes": True,
                       "prevents-read-past-end-of-share-data": True,
                       },
                     "application-version":
 str(allmydata.__full_version__),
                     }
 }}}

 Wouldn't it be more consistent for {{{maximum-mutable-share-size}}} to be
 equal to {{{remaining_space}}}? Also more meaningful to potential future
 clients that are curious about approximately big of a mutable share they
 could upload. With this version (above), they would have to look at
 {{{maximum-immutable-share-size}}} in order to answer that question, and
 they would ignore {{{maximum-mutable-share-size}}}.

-- 
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1778#comment:5>
tahoe-lafs <https://tahoe-lafs.org>
secure decentralized storage