[tahoe-dev] [tahoe-lafs] #662: change "tahoe manifest" to not skip duplicates
tahoe-lafs
trac at allmydata.org
Fri Mar 13 11:35:38 PDT 2009
#662: change "tahoe manifest" to not skip duplicates
---------------------------+------------------------------------------------
Reporter: warner | Owner:
Type: enhancement | Status: new
Priority: major | Milestone: undecided
Component: code-dirnodes | Version: 1.3.0
Keywords: | Launchpad_bug:
---------------------------+------------------------------------------------
Comment(by warner):
Oh, I should mention that partly this is the result of changing
goals/definitions of "tahoe manifest". Originally, it was intended purely
as a set of verifycaps: the idea being that you'd compute your manifest
and then hand it to a separate Verifier service, which would take
responsibility for checking up on all of them. It was also the intention
that a verifycap be usable as a repaircap, so the Verifier service could
be a Verifier/Repairer service. In these cases, we don't care about
duplicates: we just want the minimum-size set of verifycaps, and it
doesn't matter what path or paths were used to store each one.
Later, "tahoe manifest" acquired path information, because that made it
easier to backtrack and find a parent directory for any object which was
later found to have problems. About this same time, the definition of
"manifest" started changing, and now we sort of think about is as a list
of (path,cap) tuples.
So maybe we need to be more clear about our definitions, and perhaps
create a separate API for each one.
Incidentally, the cycle handling code on the "list of (path,cap) tuples"
API could respond to cycles by emitting a special marker: (type="cycle",
cap), and maybe include otherpath= too. The program which is receiving the
manifest could conceivably use this information to stitch together the
cycle somehow.
--
Ticket URL: <http://allmydata.org/trac/tahoe/ticket/662#comment:1>
tahoe-lafs <http://allmydata.org>
secure decentralized file storage grid
More information about the tahoe-dev
mailing list