Protocol core-core Version 3 » History » Revision 62
Revision 61 (Greg Burri, 03/09/2011 03:35 PM) → Revision 62/73 (Greg Burri, 03/17/2011 12:15 AM)
h1. Protocol core-core This page describes the protocol used by D-LAN Aybabtu for network communication between cores. See source:application/Protos/core_protocol.proto for message details. !network_protocol.png! h2. Downloading thread There is _NbDownloadThread_ threads. Each thread will choose a free chunk and download it. A peer cannot have more than one connection per other peer. A peer which a download is active is set as not free. <pre> F : the list of all unfinished download C : A list of chunk candidates (empty at start) - Take the first file in F -> f. Loop : If the hash chunks of f are unknown : If there is already a peer asking for hashes : - Take the next file in F -> f. - continue Else - Ask the hashes to the source (see the message 'GetHashes'). For each chunk not downloaded and not being downloaded of f -> c : If c has a free peer : - Add c to C If C isn't empty : - Take the best chunk in C based on peer.downloadRate. If there is more than one best chunk then choose one randomly. - Grab the lock for the peer - Request the download (see the message 'GetChunk') - Take the first file in F -> f. Else : - Take the next file in F -> f. </pre> h2. Updating peer to hash association This loop will periodically grab the _NumberOfChunkToUpdate_ first chunks and request to all other peers what chunk they have. If there is no chunk available the message will be send without hashes. This message is also used to know the peer on the network. <pre> F : the list of all unfinished download C : list of latest chunk hashes sent Loop : - Empty C t : Time.now n : number of chunk = 0 While take the next file in F -> f If C.count >= 'NumberOfChunkToUpdate' : - Break If we know the hashes for f : For all chunks of f -> c : - Add c to C Else : - Break - Send the list of the chunk to everyone. (The received responses will be compared against C) - Wait 'TimeBetweenChunksUpdate' - (Time.now - t) </pre> h2. Parameters Most parameters will be stored as constants in their component. The given values below are just for illustrate with an example, they will be defined in a empiric manner later. |_.Name|_.Value |_.Unit|_.Explanation/Comments| | _ChunkSize_ | 67108864 | [Byte] | (64 MB) | | _LanSpeed_ | 52428800 | [Byte/s] | (50 MB/s) | | _TimeRecheckChunkFactor_ | 4 | - | If the time to download a chunk exceeds _TimeRecheckChunkFactor_ * _ChunkSize_ / _LanSpeed_ the peers are rescanned to choose a better one (better download rate). For example : 4 * 64 / 50 = 5 second | | _SwitchToAnotherPeerFactor_ | 1.5 | - | During the recheck of the peers to choose a better one the download rate of the candidate must be above the current * 1.5. | | _DownloadRateValidTime_ | 1500 / _LanSpeed_ = 30 s | [s] | The download rate of a peer is only valid during this time after its last update. After that its rate is set to the maximum. | | _IMAliveFrequency_ | 10 s | [s] | The message _IMAlive_ is sent each 10s. | | _NbDownloadThread_ | 3 | - | Number of concurrent downloading thread. | | _BufferSize_ | 65535 | [Byte] | (64 KiB). This buffer is used when reading or writing a file. | | _TCPSocketBufferSize_ | 65535 | [Byte] | (64 KiB). Used when data are received. See _QAbstractSocket::setReadBufferSize_. | | _TCPPeerConnectionKeepAlive_ | 60 | [s] | (1 min). There's can be one or more connection to a certain peer, these connections are kept alive for a period of time. For each known peer there is a pool of connection. |