[tahoe-lafs-trac-stream] [tahoe-lafs] #393: mutable: implement MDMF
tahoe-lafs
trac at tahoe-lafs.org
Fri Feb 25 23:37:24 PST 2011
#393: mutable: implement MDMF
------------------------------+---------------------------------------------
Reporter: warner | Owner: kevan
Type: enhancement | Status: assigned
Priority: major | Milestone: 1.9.0
Component: code-mutable | Version: 1.0.0
Resolution: | Keywords: newcaps performance random-access privacy gsoc mdmf mutable backward-compatibility forward-compatibility review-needed
Launchpad Bug: |
------------------------------+---------------------------------------------
Comment (by kevan):
Replying to [comment:76 davidsarah]:
> Why have two ways to express that? I'd suggest just requiring the offset
parameter to be omitted to get whole-file replacement.
I worry about inconsistent behavior if we later allow {{{offset=append}}}
or {{{offset=some-other-thing-that-isn't-really-an-offset-
but-a-behavior}}}, since replacement would then behave differently than
other operations that would otherwise be treated similarly by the API.
That's not really well-founded, though, since we can always start to
support {{{offset=replace}}} at that point (and in any case would want to
think carefully about allowing {{{offset}}} to take strings that describe
behaviors and have little to do with offsets as values). At the moment,
what you suggest is a consistency improvement, and gives us more freedom
in the future to add other parameters for high-level behaviors instead of
overloading the {{{offset}}} parameter. Good suggestion; I'll work it into
a patch. Thanks.
--
Ticket URL: <http://tahoe-lafs.org/trac/tahoe-lafs/ticket/393#comment:78>
tahoe-lafs <http://tahoe-lafs.org>
secure decentralized storage
More information about the tahoe-lafs-trac-stream
mailing list