close
Warning:
BrowserModule failed with ConfigurationError: Look in the Trac log for more information.
- Timestamp:
-
Sep 22, 2008, 1:51:32 PM (16 years ago)
- Author:
-
Ingmar Baumgart
- Comment:
-
--
Legend:
- Unmodified
- Added
- Removed
- Modified
-
|
v4
|
v5
|
|
| 3 | 3 | |
| 4 | 4 | * '''iterative''': The originator starts a lookup by sending one (or multiple) !FindNode RPCs to the closest next hop |
| 5 | | stored in the local routing table. The received !FindNodeResponse contains better next hop nodes, which are successively queried by the originator until a !FindNodeResponse with set ''isSibling'' bit is received. Finally the message is directly sent to this sibling (= "closest node"). |
| | 5 | stored in the local routing table. The received !FindNodeResponse contains better next hop nodes, which are successively queried by the originator until a !FindNodeResponse with ''isSibling=true'' is received. Finally the message is directly sent to this sibling (= "closest node"). |
| 6 | 6 | * '''exhaustive-iterative''': This is similar to the ''iterative'' case above, but the ''isSibling'' bit is ignored. The originator instead continues to query all closest nodes, until no better nodes are returned. This increases bandwidth consumption and lookup latency, but is more secure. |
| 7 | 7 | * '''semi-recursive''': The originator encapsulates the message in a ''!BaseRouteMessage'' and forwards it to the closest next hop stored in the local routing table. The message get forwarded recursively until the sibling node (= "closest node") for the destination key is reached. An optional response to the message is sent directly to the originator. |
