[mnet-devel] idea for download strategy

[Zooko]

correction to my own post

> Second, if you don't have enough currently-outstanding "do you have blocks" 
> requests for discovering block locations, then choose the block that you most 
> want to locate (which is that?  We'll worry about it later.), and pick the best 
> blockserver for that block (how?  We'll worry about that later.), and send a "do 
> you have blocks" message to that blockserver.  It's a waste to send a "do you 
> have blocks" message with only a single blockId in it, so fill it out with the 
> best 32 blockIds for that blockserver.  (How do you choose the best blockIds for 
> a blockserver?  We'll worry about that later.)
> 
> Okay, I think that's it.  This is what BlockWrangler currently does, and all the 
> "worry about it later" parts are supposed to be delegated to a 
> BlockWranglingStrategy.

Actually, BlockWrangler doesn't currently require that you choose the best 
block, then choose the best blockserver, then fill in message with extra 
blockIds.  That is what GSR and KISS currently do, but it isn't required.  If 
someone can think of a better strategy I would be interested to hear it!

Actually, I take it back, what GSR and KISS currently do is just pick a 
blockserver (in GSR's case, a semi-random but favored blockserver, and in KISS's 
case, a truly random blockserver) and then pick blockIds that are close to that 
blockserver in the XOR metric!

So what I've proposed above is a variation of GSR.  Better?  I don't know.  :-/

--Z



-------------------------------------------------------
This SF.net email is sponsored by:
The Definitive IT and Networking Event. Be There!
NetWorld+Interop Las Vegas 2003 -- Register today!
http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en
_______________________________________________
mnet-devel mailing list
mnet-devel at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mnet-devel