Opened at 2011-08-27T18:01:28Z

Closed at 2011-09-04T21:52:07Z

#1509 closed defect (duplicate)

MDMF filecaps should tolerate extra parameters

Reported by: warner Owned by:
Priority: major Milestone: 1.9.0
Component: code-mutable Version: 1.9.0a1
Keywords: mdmf mutable forward-compatibility Cc:
Launchpad Bug:

Description

The MDMF filecap format is currently defined as: 

  URI:MDMF:$writekey:$fingerprint[(:$extension)*]

and all existing caps are created with two extension fields: the first is 'k' (as an integer), the second is segsize (also as an integer). The intention is to allow additional extension fields to be added in the future, perhaps hints that could speed up a download.

But I think I saw places in the code that fail if the number of extension fields is not either 0 or 2. These places should be fixed to tolerate 1, or 3, etc.

I'd like to have this in 1.9 because then 1.9 will be tolerant of caps generated by future versions that have a different number of extension fields.

Change History (2)

comment:1 Changed at 2011-08-28T03:40:35Z by davidsarah

  • Keywords mdmf mutable forward-compatibility added
  • Priority changed from minor to major

+1 on fixing this for 1.9.

comment:2 Changed at 2011-09-04T21:52:07Z by davidsarah

  • Resolution set to duplicate
  • Status changed from new to closed

Duplicate of #1526. Will copy the description there.

Note: See TracTickets for help on using tickets.