[tahoe-dev] [tahoe-lafs] #931: show ?-IMM and ?-RO for immutable and read-only unknown nodes in directory listings

tahoe-lafs trac at allmydata.org
Thu Jan 28 22:30:21 UTC 2010


#931: show ?-IMM and ?-RO for immutable and read-only unknown nodes in directory
listings
-------------------------------------+--------------------------------------
 Reporter:  davidsarah               |           Owner:       
     Type:  enhancement              |          Status:  new  
 Priority:  major                    |       Milestone:  1.6.0
Component:  code-frontend-web        |         Version:  1.5.0
 Keywords:  usability review-needed  |   Launchpad_bug:       
-------------------------------------+--------------------------------------
 In describing the fix for #833, Zooko said:
 > #833 also adds some very nice forward-compatibility features, so that
 when future versions of Tahoe-LAFS start uploading new kinds of
 capabilities, people using Tahoe-LAFS v1.6 will get a reasonable
 indicator showing that there is something here that is immutable, but is
 from the future so you can't actually see it, instead of getting a
 traceback or some sort of behavior that violates the deep-
 immutability property.

 However, #833 didn't actually change directory listings to show unknown
 caps as immutable (?-IMM) or read-only (?-RO). I have a patch to do that.

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


More information about the tahoe-dev mailing list