One port per torrent-file?

[ukb007]

Hi.

1. Job 1 - uTorrent is uploding a torrent at, say, port 56056.

2. Job 2 - I start a second upload from File > Create New Torrent, and it starts uploading.

3. Job 3 - Now I start a download, in the same uTorrent.

4. All three files show up in uTorrent's window.

5. The port number remains the same at Options > Preferences > Connections > Port used for incoming connections. All three jobs are using the same port number 56056.

In BitTornedo, one has to open a separate copy of the client for each download job. The port number varies in each. uTorrent can handle multiple jobs in one opened copy of the client. Is that a problem? Shouldn't we have a different port for each torrent file - whether being uploaded or downloaded?

Regards.

[TheBear]

Why do something that isn't required.

I have a 3000/800 ADSL connection and I can max it out with µTorrent using only a single port.

[Ultima]

If it were a problem, the major clients wouldn't have moved toward single-port cores.

[DreadWingKnight]

Switching to one port per torrent is not progress.

Even BitTornado's Launchmany proves that.

[ukb007]

Thanks, friends.

I think I can safely deduce from your posts that one port cab handle uploads and downloads of more than one file at a time. Is there a limit - to the number of files or to data flow (in either direction) per second?

Regards.

[TheBear]

I've had 10 active torrents on my connection. There were no issues preventing more, but my upload bandwidth was being spread too thin for my liking.

Maybe some of the uber-pipe users can offer better examples.

[Ultima]

Gigabit lines reportedly work fine with µTorrent. 100mbit lines definitely.