reduce number of active connections: connect-on-demand #444

New Issue

warner · 2008-06-03T04:55:37Z

warner commented

2008-06-03 04:55:37 +00:00

Eventually, we'll probably need to move away from the current fully-connected-mesh network and do something that will scale better. One point that we discussed was "live != connected-to-introducer, connect on demand". I think this meant that clients don't have to be connected to the introducer to be considered alive (which we've already accomplished), and that we should hold of making a connection to a storage server until we need to, and that we should drop connections when we have too many.

I'm not sure if those will work very well, but this ticket is here to remind us that our roadmap.txt used to have this issue as Connection Management step 3. (step 4 is decentralized introduction: #68, and step5 is relay)

Eventually, we'll probably need to move away from the current fully-connected-mesh network and do something that will scale better. One point that we discussed was "live != connected-to-introducer, connect on demand". I think this meant that clients don't have to be connected to the introducer to be considered alive (which we've already accomplished), and that we should hold of making a connection to a storage server until we need to, and that we should drop connections when we have too many. I'm not sure if those will work very well, but this ticket is here to remind us that our roadmap.txt used to have this issue as Connection Management step 3. (step 4 is decentralized introduction: #68, and step5 is relay)