#833: reject mutable children when *reading* an immutable dirnode
------------------------------------------------------------------------------------+
Reporter: warner
| Owner: davidsarah
Type: defect
| Status: assigned
Priority: critical
| Milestone: 1.6.0
Component: code-dirnodes
| Version: 1.5.0
Keywords: integrity forward-compatibility backward-compatibility
confidentiality | Launchpad_bug:
------------------------------------------------------------------------------------+
Comment(by warner):
If we must use prefixes, let's use {{{unknown.}}} instead of {{{unk.}}} .
We don't need these to be short, and abbreviated-to-the-point-of-
incomprehensibility keywords drive me nuts.
I don't know if the same argument applies to {{{imm.}}} or {{{ro.}}} or
whatever.
I haven't read the rest of the discussion thoroughly enough to have an
intelligent opinion, but this prefix stuff makes me nervous. OTOH, the
notion of attaching a "guard" to the cap seems to make sense. I just worry
about last-minute changes to a two-year old API.
--
Ticket URL: <http://allmydata.org/trac/tahoe/ticket/833#comment:37>
tahoe-lafs <http://allmydata.org>
secure decentralized file storage grid
_______________________________________________
tahoe-dev mailing list
[email protected]
http://allmydata.org/cgi-bin/mailman/listinfo/tahoe-dev
