[tahoe-lafs-trac-stream] [tahoe-lafs] #1373: 'tahoe cp' should not make links to existing immutable files when the encoding parameters have changed
tahoe-lafs
trac at tahoe-lafs.org
Tue Mar 1 15:49:58 PST 2011
#1373: 'tahoe cp' should not make links to existing immutable files when the
encoding parameters have changed
-----------------------------------+----------------------------------------
Reporter: davidsarah | Owner:
Type: defect | Status: new
Priority: major | Milestone: undecided
Component: code-frontend-cli | Version: 1.8.2
Resolution: | Keywords: tahoe-cp preservation availability rebalancing usability
Launchpad Bug: |
-----------------------------------+----------------------------------------
Comment (by davidsarah):
Replying to [comment:3 davidsarah]:
> Replying to [comment:2 warner]:
> > Also, if we're going to use a CLI command to do this, the brains of
the operation should probably be in the gateway anyways: you wouldn't want
the CLI tool to download the full contents of the file and then send them
right back to the same gateway.
>
> It wouldn't do that. It would compare the parameters in the URI that it
is copying with the current parameters.
I misinterpreted what you said here; I thought you were referring to the
operation to check whether the parameters have changed.
I don't see why the reencoding operation can't be optimized later.
Creating files with the requested parameters is a correctness issue, in my
view, so takes precedence over the bandwidth usage between the gateway and
the CLI process (which is normally on a local connection and so not a big
problem).
--
Ticket URL: <http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1373#comment:4>
tahoe-lafs <http://tahoe-lafs.org>
secure decentralized storage
More information about the tahoe-lafs-trac-stream
mailing list