Algorithms » History » Revision 11

Revision 10 (Greg Burri, 08/02/2009 01:34 PM) → Revision 11/35 (Greg Burri, 08/02/2009 01:35 PM)

h1. Algorithms 

 h2. Searching 

 For a functional description see here : [[Functional definition#The-search-window]] 

 h2. Peer ID 

 Each peer owns a peer id which is unique and generated during the first start. This ID is used to identify a peer, it's better than the previous usage of peer IP, considering this situation : 

 * _A_ put in queue a file entry _f_ from _B_, _B_ doesn't know the hashes of this file entry. 
 * _B_ change his IP address. 
 * _A_ want to download _f_, it can ask _B_ for the hashes even _B_'s IP changed. 

 h2. Core threads 

 There are three kind of threads in the core in addition to the main thread : 
 * [[Protocol_core-core#Downloading-thread|Downloading thread]] : @DownloadManager::ChunkDownloader@ 
 * Uploading thread : @UploadManager::Uploader@ 
 * [[Algorithms#Updating-the-file-cache|Updating Updating file cache thread]] thread : @FileManager::FileUpdater@ 

 h2. Updating the file cache 

 Here is the algorithm for the thread (@FileManager::FileUpdater@) which will periodically update the file cache and persist it. 

 D : The set of shared directories 
 T : Time during the hashes are computed (for example 30s) 
 F : A set of file initialy empty 

 Loop : 
    For each d in D (recursively) : 
       - Synchronize physical folders and files whith d content 
       - Add in F the files which doesn't have computed hashes 
    t : 
    For each f in F : 
       - Compute the unkown hash of files f 
       - Remove f from F 
       If ( - t) > T : break 
    - Wait T - ( - t) 
    - Persist the entire cache in a file 

 h2. Downloading 

 See here : [[Protocol_core-core#Downloading-threads]]