[tahoe-dev] [tahoe-lafs] #269: client should handle migrated shares by updating the write-enabler

[tahoe-lafs]

#269: client should handle migrated shares by updating the write-enabler
------------------------------+---------------------------------------------
     Reporter:  warner        |       Owner:                               
         Type:  defect        |      Status:  closed                       
     Priority:  major         |   Milestone:  eventually                   
    Component:  code-storage  |     Version:  0.7.0                        
   Resolution:  wontfix       |    Keywords:  migration leases preservation
Launchpad_bug:                |  
------------------------------+---------------------------------------------
Changes (by zooko):

  * status:  new => closed
  * resolution:  => wontfix


Comment:

 The new plan is to define a new mutable-file format (wiki:NewCapDesign)
 which doesn't have write-enablers (instead it has a digital signature
 checkable by the server), so I think we should close this as ''wontfix''.

 This means that people using the old cap format (which is everyone,
 currently) can't expect that a future version of Tahoe-LAFS will have the
 ability to fix the writer-enablers on migrated mutable shares.

-- 
Ticket URL: <http://allmydata.org/trac/tahoe/ticket/269#comment:7>
tahoe-lafs <http://allmydata.org>
secure decentralized file storage grid