This is very good to hear.

This only means that if I am about to download a few files where I know there will be many hosts available to swarm from I have to adjust the limit accordingly.

Just to clarify, does the program make any decisions based on connection speed on adjusting the max swarming amount or is it harcoded at 6?

(I have 1Mb DSL downstream (384kb upstream) connection and 8 connections would allow apprx 12,5KB per connection in optimal situation and if, in the worst case scenario, I was swarming the maximum of 6 per dl available bandwidth per connection would be around 2,1KB - overhead which would throttle the total connection almost to zero with the overhead from each)

And as from the UI perspective, you could still make this available from the options if users desires so?

And of course, if this would be implemented, it would be sensible to check if more hosts have become available for the files you're already downloading before checking the queued files when more dl slots have become available.

Of course, I realise, this does not make much sense since the worst case is almost impossible to happen. (this just came to my mind since I'm currently working on a web-application where I have to think a lot about the used bandwidth/connections, even if it is more from a database point of view