![]() |
|
Register | FAQ | The Twelve Commandments | Members List | Calendar | Arcade | Find the Best VPN | Today's Posts | Search |
XoloX Feature Request Missing something? Let us know. XoloX has been discontinued. We highly recommend you use an actively developed client instead. |
| LinkBack | Thread Tools | Display Modes |
| |||
![]() Here's an idea I had that I think would be a good feature: I would like XoloX to start with one upload connection only, then if that user is not averaging > 20KB from me, allow a second connection. If those two don't average > 20KB combined, allow a third, etc. The benefit of this is that it would let people that connect to you download as fast as possible while still using your entire bandwidth. If you were a modem user, XoloX could use 3k in the calculations and so on. - JL |
| |||
![]() Similar proposals have been brought up in the past, but the developers have said that it's a bit too complicated for their tastes. I guess I'll just have to make my own client... now where's that 'programming for dummies' book? |
| |||
![]() The programmers actually said that? What I propose *really* isn't complicated at all. I could do it if this was a C/C++ monster - Unfortunately I've never seen Delphi code. In the same thread that XoloX updates the average upload speed, it simply needs to keep a second, longer-intervalled, average of the totals of the individual averages. Then, it could compare that total to the predetermined Max, minus the total bandwidth being used by the link connections to the gnutella network (and possibly minus some other small percentage for fluctuations). The only 'complicated' part of this, as far as I can see, is determining the connections max upload capacity. I know they want the value to be truthful, but I don't see any problem with letting the user specify/change this in an options dialog. After all, having it set very low will *not* stop your total bandwith from being used by a single connection, it will merely stop additional connections from robbing the bandwidth currently going to that first user. At the end of every download, XoloX could then subtract 1 from the number of currently allowed upload connections, and let the aforementioned comparison determine if the connection should be re-added. Of course, there should be some maximum number of connections (max upload capacity / 1 ?) to prevent a glitch from allowing hundreds of uploads - giving everyone almost zero bandwidth. -JL www.eternaldusk.com |
| |
![]() | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
[feature] speed throttle based on upload average | arne_bab | New Feature Requests | 0 | April 13th, 2003 04:27 AM |
No upload bandwidth | RABIES | Download/Upload Problems | 8 | September 20th, 2002 02:32 PM |
request: option to limit bandwidth | steronius | Support: General | 1 | June 21st, 2002 05:47 PM |
upload bandwidth | irregularjoe | Download/Upload Problems | 0 | May 10th, 2002 08:27 PM |
Upload Bandwidth | Unregistered | Open Discussion topics | 1 | September 10th, 2001 04:19 PM |