We think the message "try again later" is nowhere near telling the clients to
never reconnect and we indeed suppose this is a fix for the problem and we
added it so in the changelog of ADCH++.
Additionally, there were an actual case where the hub owner's problem solved
this way.
We see this is
Bug #1088638 status changed in ADCH++:
Won't Fix => Fix Committed
https://bugs.launchpad.net/adchpp/+bug/1088638
"Not enough bandwidth available, please try again later"
This bug is linked to #690223.
Not enough bandwidth available, please try again later
https://answers.launchpad.net/adchpp
My original issue was about sending the TL -1 parameter and thus telling
the clients to never reconnect in case of overflow (even though the
error message shown to the user conflicts with that). If that is the way
how it's supposed to work, I'd rather set a different status for the
issue. Documenta
Bug #1088638 status changed in ADCH++:
Fix Committed => Won't Fix
https://bugs.launchpad.net/adchpp/+bug/1088638
"Not enough bandwidth available, please try again later"
This bug is linked to #690223.
Not enough bandwidth available, please try again later
https://answers.launchpad.net/adchpp
4 matches
Mail list logo