use mkdir-immutable in "tahoe backup" #828

New Issue

warner · 2009-11-12T00:38:39Z

warner commented

2009-11-12 00:38:39 +00:00

The new APIs in #607 should be used by the frontend "tahoe backup" CLI command. This will make it run considerably faster (no RSA keypair generation for each directory, and fewer roundtrips between the CLI and the webapi sides).

It was always my intention for "tahoe backup" to create immutable directories, but because we didn't have them until very recently, I had to fake it by creating a regular mutable directory and then throwing away the writecap. Now that #607 is done, we can do it properly.

The new APIs in #607 should be used by the frontend "tahoe backup" CLI command. This will make it run considerably faster (no RSA keypair generation for each directory, and fewer roundtrips between the CLI and the webapi sides). It was always my intention for "tahoe backup" to create immutable directories, but because we didn't have them until very recently, I had to fake it by creating a regular mutable directory and then throwing away the writecap. Now that #607 is done, we can do it properly.

warner added the

labels 2009-11-12 00:38:39 +00:00

warner added this to the 1.6.0 milestone 2009-11-12 00:38:39 +00:00

warner commented

2009-11-20 04:10:21 +00:00

Splitting this ticket into two. #836 contains the '"tahoe cp -r" should use mkdir-with-children' portion. This one is now just about "tahoe backup", and how it should use mkdir-immutable.