Whoo-hoo! Way to go Brian! Immutable directories are in (#607)! But is there a way for users to use them, such as through the CLI or WUI?
Do the tests for #708 already cover everything that came out of the #607 work? I guess the release notes will explain that if you create an immutable directory then put it into a directory and then let a v1.5 clients view that directory then they will see -- what, a child name with no attached hyperlink, so it shows the existence of a child by that name but they can't click on it? And v1.4 clients will be unable to browse the directory containing such children at all -- if they look at that directory then they'll get an exception instead of a directory listing. What does the v1.5 CLI show when you "tahoe ls" a directory containing immutable directories? Let us know how we can manually test the new immutable directories to make sure they've been properly banged on in practice before a new stable v1.6 release. Of course, one of the best ways would be to use #606 -- a super efficient and secure backup tool. :-) But that's not done yet. And we should bang on it in other ways, too. Regards, Zooko http://allmydata.org/trac/tahoe/ticket/606# backupdb: add directory cache http://allmydata.org/trac/tahoe/ticket/607# DIR2:IMM http://allmydata.org/trac/tahoe/ticket/708# graceful handling of capabilities in a format from the future that you can't understand _______________________________________________ tahoe-dev mailing list [email protected] http://allmydata.org/cgi-bin/mailman/listinfo/tahoe-dev
