[tahoe-dev] [tahoe-lafs] #816: don't rely on notifyOnDisconnect()

tahoe-lafs trac at allmydata.org
Wed Oct 21 15:36:32 PDT 2009


#816: don't rely on notifyOnDisconnect()
--------------------------+-------------------------------------------------
 Reporter:  zooko         |           Owner:           
     Type:  enhancement   |          Status:  new      
 Priority:  minor         |       Milestone:  undecided
Component:  code-network  |         Version:  1.5.0    
 Keywords:                |   Launchpad_bug:           
--------------------------+-------------------------------------------------

Comment(by warner):

 I like the ping-all-servers button on the welcome page. I'm happy with not
 using {{{notifyOnDisconnect()}}} to update the welcome-page information in
 a timely manner (if people want timely information, they can push the
 button and reload). It might be nice for the welcome page to show "waiting
 for ping response.." while a ping is in flight, but on the other hand that
 might also be uglier and unnecessarily complicated.

 I haven't yet decided about removing the {{{notifyOnDisconnect()}}} calls
 which provide share-allocation with more-timely information about how to
 allocate share numbers. I think I want peer-selection to have reasonably
 timely information about which servers are likely to be available and
 which ones are not, to improve the chances that the shares get allocated
 in order. (in addition to providing useful forensic data later, it also
 marginally improves performance of download, because the downloader is
 more likely to get "primary" shares sooner).

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


More information about the tahoe-dev mailing list