[tahoe-lafs-trac-stream] [tahoe-lafs] #1363: refactor storage_client.py, use IServer objects instead of rrefs

[tahoe-lafs]

#1363: refactor storage_client.py, use IServer objects instead of rrefs
------------------------+---------------------------------------------------
     Reporter:  warner  |       Owner:  zooko        
         Type:  task    |      Status:  assigned     
     Priority:  major   |   Milestone:  undecided    
    Component:  code    |     Version:  1.8.2        
   Resolution:          |    Keywords:  review-needed
Launchpad Bug:          |  
------------------------+---------------------------------------------------

Comment (by warner):

 cool, I'll add "server_selection_index" to my TODO list for this ticket.
 My only problem with it is the acronym collision: we use "storage index"
 and "SI" in lots of places, and it'd be nice to have something for this
 that didn't have quite so many Ss and Is in it. But yeah, let's talk it
 over on the list.

 SHA1: hmm, good question. We started out using stdlib {{{sha.new}}} (which
 is SHA1), and never changed it (because to change it would mess up server-
 selection ordering for existing filecaps). It doesn't need to be secure,
 as it's just a load-balancing tool, but it would be nice to use the same
 hash function everywhere. Maybe when #466 gets us to the point of defining
 a new server-selection-seed (which could be a new name for peer-selection-
 index), we could say that old SSSs use SHA1 and new SSSs use SHA256.

-- 
Ticket URL: <http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1363#comment:5>
tahoe-lafs <http://tahoe-lafs.org>
secure decentralized storage