Due to a new feature recently introduced into Bitcomet’s torrent maker, people who do not use BitComet (the majority) are sometimes forced to download so called “padding files†which is — for them — a waste of time and bandwidth.
So what are these padding files?
For every file in a multi-file torrent, BitComet includes a padding file by default. This overcomes the problem of ending one file and beginning another on the same BitTorrent “piece.†The feature was added to support finding sources from http/ftp/ed2k services on multi-file torrents.
For example, if BitComet users are downloading a set of .mp3 files, it tries to get some of those files from a non-BitTorrent source if possible. This is good both for the (BitComet) user and the swarm. However, the implementation of these padding files create problems for non-Bitcomet clients and the web sites that carry information from the *.torrent files.
|
|
|
1
Flipper said
September 28 2007 @ 11:02 pm
Personally, I find it extremely annoying. I have spent the last week downloading a 28GB archive of 156 files (yes, twenty-eight gigs) when it suddenly stopped at 67%. I cleared the torrent and restarted it, thinking it may have lost the tracker… instead, I am forced to download collection of 156 padding files, and now I’m only 35% through… fu[k BitComet! Someone needs to raid their site and send their webmaster a virus.
2
Flipper said
September 28 2007 @ 11:03 pm
I have spent the last week downloading a 28GB archive of 156 files (yes, twenty-eight gigs) when it suddenly stopped at 67%. I cleared the torrent and restarted it, thinking it may have lost the tracker… instead, I am forced to download collection of 156 padding files, and now I’m only 35% through… fu[k BitComet! Someone needs to raid their site and send their webmaster a virus.