Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
long-time_seeding [2010/12/19 01:39] greywizard |
long-time_seeding [2011/01/06 09:25] lucy removed |
||
|---|---|---|---|
| Line 7: | Line 7: | ||
| LT-Seeding upload is done through the LT-Seeding protocol which is proprietary to BitComet. LT-Seeding upload is independent of the upload done through the BitTorrent protocol and can be done in parallel with that or alone, depending on the state of the task (seeding or stopped).\\ LT-Seeds are peers 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 and remain 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 upload is done through the LT-Seeding protocol which is proprietary to BitComet. LT-Seeding upload is independent of the upload done through the BitTorrent protocol and can be done in parallel with that or alone, depending on the state of the task (seeding or stopped).\\ LT-Seeds are peers 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 and remain 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 (the equivalent of a tracker, in the BitTorrent protocol) 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. | + | LT-Seeding clients use a server (the equivalent of a tracker, in the BitTorrent protocol) 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 file of the task.\\ |
| + | If that option is enabled (see below), then at the creation of any // | ||
| + | For // | ||
| * // | * // | ||
| Line 15: | Line 18: | ||
| * //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】 | * //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. | + | **Requirement for Long-Time Seeding**: A BitComet client must have an open port! LAN users must make sure they have an open port (i.e. the status light is green). If you don't have an open port yet and don't know how to open it check [[bitcomet_client_issues_and_possible_solutions# |
| **Choosing the Long-Time Seeding protocol**: In //Options -> Advanced// you can choose the transport protocol for LT-Seeding, by using this option: // | **Choosing the Long-Time Seeding protocol**: In //Options -> Advanced// you can choose the transport protocol for LT-Seeding, by using this option: // | ||
| | | ||
| - | BitComet | + | BitComet |
| - | For // | + | |
| [[cometid# | [[cometid# | ||
