[tahoe-lafs-trac-stream] [tahoe-lafs] #1526: make sure the new MDMF extension field is forward-compatible and safe

[tahoe-lafs]

#1526: make sure the new MDMF extension field is forward-compatible and safe
-------------------------+-------------------------------------------------
     Reporter:  zooko    |      Owner:  warner
         Type:  defect   |     Status:  closed
     Priority:           |  Milestone:  1.9.0
  critical               |    Version:  1.9.0a1
    Component:  code-    |   Keywords:  forward-compatibility mdmf design-
  mutable                |  review-needed review-needed
   Resolution:  fixed    |
Launchpad Bug:           |
-------------------------+-------------------------------------------------

Comment (by zooko):

 Re: comment:15 that sounds good! It means that code which is going to
 consume caps and later produce them again has to keep a verbatim copy of
 the (string) cap that they started with. But, this is a question of how
 storage and reproduction of caps should be implemented -- it is orthogonal
 to the question of whether that storage and reproduction should include or
 omit the extension field.

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