Changes between Version 26 and Version 27 of NetDB/NextBackend


Ignore:
Timestamp:
Jun 2, 2013 12:10:40 PM (6 years ago)
Author:
hottuna
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • NetDB/NextBackend

    v26 v27  
    104104K-buckets need to be continually updated.
    105105In the case of iterative searching, this is not a problem. But when doing recursive searches, the search originator will not get the usual information about nodes that are close to the queried key. [[BR]]
    106 [6] suggests to solutions to this issue.
    107 '''Source: Direct Mode'''  [[BR]]
    108 '''Source: Source-Routing Mode'''  [[BR]]
     106[6] suggests two solutions to this issue: [[BR]]
     107'''Source: Direct Mode''': All nodes on the routing path send back ''k'' nodes that are close to ''key'' back to the originator of the query. [[BR]]
     108'''Source: Source-Routing Mode''': All nodes on the routing path send back ''k'' nodes that are close to ''key'' back to the previous hop on routing path which appends its own ''k'' closest nodes to ''key'' and repeats. [[BR]]
    109109
    110110
    111111== Further work ==
    112112==== Use the locally known nodes as for routing ====
    113 If we have nodes in our local NetDB that have distance, d,,xor,, , that is lower than any distance found in the Kademlia routing tables they are good candidates for FIND_VALUE querying. However to find such candidates, the local NetDB has to be sorted, which is expensive.
     113If we have nodes in our local NetDB that have distance, d,,xor,, , that is lower than any distance found in the Kademlia routing tables they are good candidates for FIND_VALUE querying. However to find such candidates the local NetDB has to be sorted, which is expensive.
    114114
    115115[[BR]][[BR]]