On 6/13/09 1:40 PM, Zooko O'Whielacronx wrote: > > Fortunately this last one is also the easiest to implement in a robust > way -- we simply need to define a special "freeze" message that puts a > mutable file or directory into a state where it can't be changed again > (including that it can't be unfrozen). If I had that, then after > updating my old blog to announce that it had moved to a new location, > I could freeze it and would then be safe from the danger that someone > else would take it over and make updates to it in my name. >
Is this not the same as simply 'forwarding' the write capability to the read capability? And since the read is derivable from the write... Terrell _______________________________________________ tahoe-dev mailing list [email protected] http://allmydata.org/cgi-bin/mailman/listinfo/tahoe-dev
