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

 I'm inclined to think that we should only be parsing caps with
 {{{uri.py}}} if we're about to consume them somehow, and never re-
 stringify them unless we've just created one (i.e. uploaded a new file).
 Then we won't be obligated to have {{{uri.py}}} retain information that it
 doesn't actually use.

 Things like directory-listing should just dump the filecap strings.

 In fact, I kind of regret having URI objects in the first place.. they're
 really just a was to encapsulate the parsing/serialization functions.
 Having a separate class has caused a lot of confusion in things like
 {{{filenode.py}}}'s {{{get_uri()}}} method (does it return a string? a URI
 object?). So I'd like to reduce their use, and eventually get rid of them
 completely, somehow.

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