Since I was using the connection collumn to see who was using/abusing their bandwidth limiter, I was hoping there's a fix for this thing in the next release ? I'm kinda used to knowing who's using their speedlimiters ya know. A choice in this would have been nice, but I assume that's not gonna happen.
1.3.4 connection detection ?
Started by markd, Jul 07 2010 04:51 PM
2 replies to this topic
#1
Posted 07 July 2010 - 04:51 PM
Since I was using the connection collumn to see who was using/abusing their bandwidth limiter, I was hoping there's a fix for this thing in the next release ? I'm kinda used to knowing who's using their speedlimiters ya know. A choice in this would have been nice, but I assume that's not gonna happen.
#2
Posted 07 July 2010 - 05:14 PM
I have noticed that too. I wonder what is the speed in the connection column based on. Is it sent to the hub or just displayed in my client?
ApexDC++ rulez!
#3
Posted 07 July 2010 - 08:50 PM
Mek, on 07 July 2010 - 05:14 PM, said:
I have noticed that too. I wonder what is the speed in the connection column based on. Is it sent to the hub or just displayed in my client?
I'll double check all of this the change that results in the change of display received a last minute fix... the goal of the change being to unify connection display between ADC and NMDC when possible and also to fix connection sorting.
Had a quick look, looks like overlooked NMDC a bit (read: people should just move to ADC) will make sure it works as intended in NMDC with next version. Also considering that there was no definite plans for another 1.3.x release before 2.0 so you can expect it to be released as soon as I verify the fix.
To answer Meks question it just coverts the x.yyy connection type coming from hub tgo KiB/s
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users











