Re: [Blocks-development] Life Signs

[Blat F. <pet...@ho...>]

>From: "Tod D. Ihde" <to...@je...>
>To: blo...@li...
>Subject: Re: [Blocks-development] Life Signs
>Date: Sat, 12 May 2001 21:50:46 -0500
>
>
>Why should a node advertise a file? Why not just have the node advertise 
>that it can GET to a file? The node _requesting_ a file can start the 
>request on all nodes, and choose the fastest-responding node to get the 
>file
>from (and shut down the others). This allows the client to choose where it 
>gets the file from (to a degree, each node in the chain would be choosing 
>the fastest next-hop), and eliminates the "this node is storing/inserting
>this file/block" problem, because you are only advertising that you _know_ 
>about a file and can get to it, not its route. Each node would only know 
>that it's neighbor knows how to get to a block/file, not what its neightbor
>actually has in it's cache.

IMHO... Blocks needs route information because its a relay
network rather than a direct P2P network. The issue of
'the fastest route' has come up several times before,
and I think its generally agreed that using the
length of the route to work this out isnt very sensible.
I think the only real way of working out the fastest
route would be to do something akin to what GoZilla!
does... test multiple routes and measure average speed,
then choose the best one. Allowing multiple simultaneous
downloads would be a feature of an advanced GUI rather
than an inherent Blocks feature.

Its interesting revisiting these issues :-)

ttfn

PG.

_________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.