We decided to fix this problem differently than maksis suggests so the behavior
don't change and in an out of bandwith case users still aren't automatically
hammering the hub. Rather we changed a constant to a new configurable parameter
and documented the issue, along with other possible cases, when scaling the
hub's resouce usage is needed.
See commits
https://sourceforge.net/p/adchpp/code/ci/68e99c987292859ff923ac8ff49c19877262ba39/
and
https://sourceforge.net/p/adchpp/code/ci/d4a4e2fe8398c19b4ddb0bd3ac3933fcd3e57255/
** Changed in: adchpp
Status: New => Fix Committed
--
You received this bug notification because you are a member of
Dcplusplus-team, which is subscribed to ADCH++.
https://bugs.launchpad.net/bugs/1088638
Title:
Not enough bandwidth available, please try again later
Status in ADCH++:
Fix Committed
Bug description:
The error "Not enough bandwidth available, please try again later" in
ClientManager::verifyOverflow shouldn't be sent with the "TL -1"
param, as quite a few users receive that error after the hub has been
restarted.
Because of that it takes a long time to get all users back in the hub
as their clients won't reconnect automatically.
To manage notifications about this bug go to:
https://bugs.launchpad.net/adchpp/+bug/1088638/+subscriptions
_______________________________________________
Mailing list: https://launchpad.net/~linuxdcpp-team
Post to : linuxdcpp-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~linuxdcpp-team
More help : https://help.launchpad.net/ListHelp
