<div class='quotetop'>QUOTE(gregor @ Dec 6 2006, 10:25 AM) [snapback]270468[/snapback]</div>
Quote:
|
<div class='quotetop'>QUOTE(Titan @ Dec 6 2006, 05:40 AM) [snapback]270461[/snapback]
|
Quote:
Both have the option to select what to download in the torrent, and in what order.
[/b]
|
well that's a neat function! how does utorrent handle interrupted transmissions? e.g. if computer reboots for no good reason. or if it crashes? does it have bo start again form beginning (or from the place where it stopped previously)? or does it save continuously so that it can start over form the last save before the computer crashed?
[/b][/quote]
Seems like you don't have much experience of how a torrent work
The target file(s) or whatever, is broken down into peices, usualy around 1-60 KB / peice.
Then the torrent client seeks for ANY peice in any order.
Once the peice is retrived and the hash is confirmed and adds up as it should if the peice is uncorrupted by the transfere, the peice is added to the local copy you'r building.
So.. If you accidently shut down or the computer screws up, all confirmed peices are there next time you boot, and only the once that wasn't compleated is lost.
The file(s) you'r downloading are not done until the torrent is at 100%. In theory you could get stuck at 99.99% with all files in the target not compleate, OR you could have 97% and have all essential files done, and perhaps only some stuff you didn't need anyway, not ready.
Your client will request no specific peices unless you define what to download first. And when you are downloading, you are not (usualy) downloading the entire copy from ONE person, but rather a large number of ppl, most of them with only partial copies, as any peice, once it's done, is in the swarm as a share.
If you are finished, and you have un Upload/download ratio of 400% (uploaded 4 times the ammount you've downloaded), the chanses are pretty good you actualy didn't share every single peice, but rather peices that wasn't shared by others.
This is all to ensure that the most requested peice is quickly compensated and eliminating bottlenecks in the swarm.
Example: User A starts sharing a file concisting of 10 peices, all numberd 1 to 10.
User B downloads peice 1 from A
User C downloads peice 6 from A
User D downloads peice 2 from A
now..
User B downloads peice 6 from C
User D downloads peice 3 from A
User C downloads peice 1 from B
and so on... It eases the load from the innitial sharer.
Essentialy a user can share his file X by downloading it once to an infinit number of ppl, as they themselves share amongst each other in the swarm.