Update of bug #10967 (project wesnoth):
Status: None => Wont Fix
_______________________________________________________
Follow-up Comment #2:
Your bug is unfixable.
We can't eliminate the connection timeout entirely or provide a toggle to the
download client that switches it off, if only because doing that would open up
trivial ways to run a denial-of-service attack against the server.
That means all we could do is lengthen it by a fixed amount the client can't
alter. Getting that timeout right is hard; if we set it high we make service
failures due to accidental resource exhaustion or deliberate DOS more likely,
and if we set it low some crappy network somewhere is going to have stallouts
and we'll get bug reports like yours.
In fact it's quite possible the "too high" and "too low" ranges overlap.
I'm going to mark this "Wont Fix". If you can make a more specific proposal
about the timeout length that would solve your problem, please file a bug
with that number in it. Please also provide some data on your stallout-time
vs. frequency statistics; what we probably need to do is set the timeout so
it's just more that two sigmas out on your curve.
_______________________________________________________
Reply to this item at:
<http://gna.org/bugs/?10967>
_______________________________________________
Message sent via/by Gna!
http://gna.org/
_______________________________________________
Wesnoth-bugs mailing list
[email protected]
https://mail.gna.org/listinfo/wesnoth-bugs
