[tahoe-dev] [tahoe-lafs] #713: tahoe make-verify-cap

[tahoe-lafs]

#713: tahoe make-verify-cap
-------------------------------+--------------------------------------------
 Reporter:  zooko              |           Owner:           
     Type:  enhancement        |          Status:  new      
 Priority:  major              |       Milestone:  undecided
Component:  code-frontend-cli  |         Version:  1.4.1    
 Keywords:                     |   Launchpad_bug:           
-------------------------------+--------------------------------------------

Comment(by swillden):

 Replying to [comment:5 warner]:
 > Ah, ok, so it needs to be a lot like "tahoe put", but without the
 network part.
 >
 > Would {{{tahoe put --dry-run FILE}}} be reasonable, if it emitted the
 filecap just like
 > {{{tahoe put FILE}}}?

 That would work, though I'm using the web API rather than the command line
 interface.

 I am still somewhat skeptical about whether or not performance would be
 acceptable, particularly on low-end backup appliances (think Linksys with
 USB-attached storage).  SHA-256d hashing is CPU-bound on the one I've
 played with, and I get the idea that the full "PUT" operation would be
 around an order of magnitude slower.

 The need to have read cap index files has driven me to find other uses for
 them as well, uses that I'd have to find some other way to implement if I
 didn't have them, so between the performance issue and that one, I'm not
 sure I'd use a "dry run" option, even if it existed.

-- 
Ticket URL: <http://allmydata.org/trac/tahoe/ticket/713#comment:6>
tahoe-lafs <http://allmydata.org>
secure decentralized file storage grid