[tahoe-lafs-trac-stream] [tahoe-lafs] #1568: S3 backend: [storage]readonly is documented but ignored

[tahoe-lafs]

#1568: S3 backend: [storage]readonly is documented but ignored
-------------------------+-------------------------------------------------
     Reporter:           |      Owner:  zooko
  davidsarah             |     Status:  assigned
         Type:  defect   |  Milestone:  1.10.0
     Priority:  major    |    Version:  1.9.0b1
    Component:  code-    |   Keywords:  s3-backend readonly storage lae
  storage                |  review-needed
   Resolution:           |
Launchpad Bug:           |
-------------------------+-------------------------------------------------

Comment (by zooko):

 I reviewed attachment:s3-remove-readonly.darcs.patch and give it +1. I
 *would* feel better if the two {{{TODO}}}'s mentioned in that patch (one
 just in line of context) were ticketed and had {{{TODO}}}'ed unit tests...

 For what it is worth, I increasingly think read-only storage should be
 deprecated for all backends, and people will have to learn how to use
 their operating system if they want readonliness of storage. When we
 invented the read-only storage option, I think partly we were thinking of
 users who could read our docs but didn't want to learn how to use their
 operating system to set policy. Nowadays I'm less interested in the idea
 of such users being server operators.

 Also, the fact that we've never really finished implementing read-only
 storage (to include mutables), so that there are weird failure modes that
 could hit people who rely on it is evidence that we should not spend our
 precious engineering time on things that the operating system could do for
 us and do better.

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