[tahoe-lafs-trac-stream] [tahoe-lafs] #1304: 'tahoe cp' copying to a mutable file should replace the contents

[tahoe-lafs]

#1304: 'tahoe cp' copying to a mutable file should replace the contents
-----------------------------------+--------------------------------
     Reporter:  davidsarah         |      Owner:  kevan
         Type:  defect             |     Status:  new
     Priority:  major              |  Milestone:  1.9.0
    Component:  code-frontend-cli  |    Version:  1.8.1
   Resolution:                     |   Keywords:  tahoe-cp usability
Launchpad Bug:                     |
-----------------------------------+--------------------------------

Comment (by davidsarah):

 Replying to [comment:10 kevan]:
 > (another initially attractive option is a sanity check performed on
 {{{tahoe cp}}}'s targetmap before copying starts. Based on this, we could
 either abort the copy operation or print a warning if we found a readonly
 mutable target. All of that would rely upon JSON gathered from a different
 HTTP request than the request(s) actually modifying data, though, so any
 check would be inherently unreliable.

 Yes, that's a general problem with trying to make distributed operations
 have all-or-nothing semantics. Anyway, even if this could be improved, we
 don't need to do so for 1.9.

-- 
Ticket URL: <http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1304#comment:12>
tahoe-lafs <http://tahoe-lafs.org>
secure decentralized storage