[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:
         Type:  defect   |     Status:  new
     Priority:           |  Milestone:  1.9.0
  critical               |    Version:  1.9.0a1
    Component:  code-    |   Keywords:  forward-compatibility mdmf design-
  mutable                |  review-needed
   Resolution:           |
Launchpad Bug:           |
-------------------------+-------------------------------------------------

Comment (by davidsarah):

 I'm a bit confused as to what optimizations are available from including K
 and segsize in the cap. Doesn't the downloader get K and segsize on the
 first round-trip anyway? Why would it be helpful to know them before that?

 For any future extensions, I would prefer each field to be labelled. A
 one-letter label as the first character of the field would probably be
 sufficient. The advantage of this is that if we decide that a particular
 field is no longer necessary, we can just omit it without making the parse
 ambiguous.

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