Editing Intelligent chunk selection
From EMule Wiki
Warning: The database has been locked for maintenance, so you will not be able to save your edits right now. You may wish to cut-n-paste the text into a text file and save it for later.
The administrator who locked it offered this explanation: site maintenance
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 1: | Line 1: | ||
− | With Intelligent Chunk Selection users exchange | + | With Intelligent Chunk Selection users exchange infos about what chunk is being downloaded ATM, then a user can choose the less-downloaded (priority: spread the file faster). |
+ | Abbrevisation: ICS. | ||
− | + | In ICS the user preference "first/last chunk" take importance only when there are NO rare chunks (priority: spread the file). | |
− | In | + | In release-mode one, then you will choose the shortest-to-complete chunk that is not being downloaded ATM by any other client. |
− | + | This increase the probability you and the other clients would have downloaded different chunks and keep (globally) a complete source for the file, though a couple of sources quit... | |
− | + | * Detail view of parts spreading with double click on file in shared files window | |
− | * | + | There are 3 possibility : |
+ | * RELEASE : complete source <= 3: priority to Upload/Download the rarest chunks. | ||
+ | * SPREAD : complete source between 4 and 10: little chunk first, rare chunk after | ||
+ | * SHARE : complete source under 10: normal behaviour (ECS or first/last) | ||
− | + | (by enkeyDev) | |
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + |