The more I stay here the more questions I have. I was over at Rucks blog and read some on this as well...what is "seeding"?
Torrents are little bitty files that contain information about where the file can be procured on the p2p network. You don't upload the files themselves on a p2p network; rather, you share them between individuals (peers) connected to the p2p (peer-to-peer) network.
If I upload a torrentX for fileY, torrentX contains only the pathways back to the directory on my own network that I have 1) designated as containing fileY, and 2) designated as sharable with the p2p network.
After you upload torrentX, you'll want to "seed" a few uploads of the file prior to disconnecting from the network. That way, the uploaders can also "seed" torrentX, since they now have fileY in their designated directory.
This model relieves the networks of the responsibility of maintaining the hardware required to host big files while, at the same time, allowing peers to connect with one another to share our private files.
Not unlike Limewire, but with the added benefit that you won't need to act as a server after others can and will act as a server on behalf of fileY once you've given them a chance to upload it from your drives.
The Torrent network is a server for your torrentX, but you are the acting server for the actual fileY whilst you seed it.
Once a few uploads have happened, the torrent app and the network will connect to as many seeds (i.e. your peers who have uploaded your fileY and are online with the torrent app open and allowing seeding from their own drive) to complete further upload requests as quickly as possible. For example, if someone is trying to get your fileY from a torrent network, his app will execute the instructions in torrentX to seek out as many seeds as possible for parallel transfer of various data parts to reconstruct fileY.
whew!
Hope that made sense.
Best,
Sine