Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| long-time_seeding [2010/12/19 00:11] – greywizard | long-time_seeding [2011/01/06 09:25] (current) – removed lucy | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ===== Long-Time Seeding ===== | ||
| - | **Long-Time Seeding,** a unique feature of BitComet, helps users to get data from peers who have 100% of the torrent contents. For some out-dated torrents, it's common that there are no seeds, and without that if the number of aggregate copies of the files for that torrent is lower than 1, then the task can not be finished. It's Long-Time Seeding that may save you from waiting forever for seeds to join the swarm, by asking former peers which have 100% of the torrent file(s) to upload through Long-Time Seeding even if the task is stopped in their client. | ||
| - | |||
| - | LT-Seeding upload is done through the LT-Seeding protocol which is proprietary to BitComet. LT-Seeds are clients which hold 100% of the files for the task **irrespective** whether the task is in an active state (seeding) or stopped. That is to say, if LT-Seeding is enabled in BitComet //Options// and also enabled for a particular task, then once that task has finished downloading the client will become an LT-Seed for that task until the task is deleted from the Task List (or until LT-Seeding is manually disabled, either individually for that task or globally in BitComet // | ||
| - | |||
| - | LT-Seeding clients use a server for querying and finding peers (LT-Seeds) for the tasks which have LT-Seeding enabled. This is done by using a unique LT-hash which is being computed for every task. This could be viewed as the equivalent of a tracker, in the BitTorrent protocol. | ||
| - | |||
| - | * // | ||
| - | |||
| - | * //Auto Upload Rate Control//: In all the later versions of BitComet you can choose to let the client manage the bandwidth allocated to LT-Seeding upload, automatically. The client will use any unused upload bandwidth (up to the maximum upload rate set in Options--> | ||
| - | |||
| - | * //Upload rate limit for Long-Time Seeding//: If you wish to manually control and assign bandwidth for LT-Seeding upload, you can limit the upload rate using this option. 【Overall upload rate limit has higher priority than the Long-Time Seeding upload rate limit】 | ||
| - | |||
| - | **Requirement for Long-Time Seeding**: A BitComet client must have an open port! LAN users must enable this function after [[add_port_mapping_in_nat_router|Adding Port Mapping]] and the status light became green. | ||
| - | |||
| - | * //Choose Long-Time Seeding protocol//: In //Options -> Advanced// you can choose the transport protocol for LT-Seeding using this option: // | ||
| - | | ||
| - | BitComet automatically searches for Long-Time seeds for a BitTorrent task that is using a torrent made by BitComet.【Only suitable for BitComet Client】\\ {{: | ||
| - | |||
| - | [[cometid# | ||
| - | |||
| - | You can watch real-time info about the speed at which your client is uploading by LT-Seeding, in the [[bitcomet_detailed_info_pane# | ||
| - | |||
| - | However when your client is downloading through LT-Seeding, that speed is added to your download speed in the Task View pane, as well. You can watch the connected LT-Seeds and the speed at which you're downloading from them, in the [[bitcomet_detailed_info_pane# | ||
| - | |||
| - | ---- | ||
| - | -[[http_ftp_batch_download|Previous Page]] -[[preview_while_downloading|Next Page]]\\ | ||
| - | -[[start|Main Index]] | ||
