[tahoe-dev] [tahoe-lafs] #958: LAFS 301 Moved Permanently

[tahoe-lafs]

#958: LAFS 301 Moved Permanently
----------------------------------------------------------------------------------------------------------------------------------------+
 Reporter:  zooko                                                                                                                       |           Owner:            
     Type:  enhancement                                                                                                                 |          Status:  new       
 Priority:  major                                                                                                                       |       Milestone:  eventually
Component:  code-mutable                                                                                                                |         Version:  1.6.0     
 Keywords:  forward-compatibility backward-compatibility integrity newcaps newurls http sftp ftpd smb availability security revocation  |   Launchpad_bug:            
----------------------------------------------------------------------------------------------------------------------------------------+

Comment(by davidsarah):

 Replying to [comment:10 zooko]:
 > Replying to [comment:4 davidsarah]:
 > > All storage servers must be running Tahoe-LAFS v1.7 or later,
 > > otherwise this command will fail.
 >
 > Maybe this backwards-incompatibility won't be necessary! I think there
 might be an extensible structure, the contents of which the storage
 servers will pass on to downloaders without needing to understand the
 contents themselves.

 How would older servers know to refuse to update a share? Temporary
 redirect wouldn't require upgrading servers, but we can't see how to avoid
 that for permanent redirect (if it is to be usable for revocation).

 > In particular, I think maybe the UEB (someday to be renamed CEB when
 "URI" gets renamed "Capability" everywhere) can hold the new 301
 redirection marker and the new cap that this cap has been redirected to.

 Yes, that's a viable alternative design to putting the marker in the
 metadata, but it doesn't seem to solve the problem of older servers still
 accepting share updates.

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