Follow-up Comment #1, bug #23083 (project wesnoth):
I looked into this issue. It's caused by the way networking code is tracking
progress. It relies on completion handlers from asio's async_write/async_read,
but in case of windows asio calls completion handler only once per write
operation. Read operation on windows work in the same way as on linux so
completion handlers still work to track download progress. I didn't see any
guarantees on when completion handler is called in asio's documentation so the
safe way to fix it is to manually split write and read operations into small
chunks, but it'll make code more complex and duplicate something asio should
be doing itself IMO.
_______________________________________________________
Reply to this item at:
<http://gna.org/bugs/?23083>
_______________________________________________
Message sent via/by Gna!
http://gna.org/
_______________________________________________
Wesnoth-bugs mailing list
[email protected]
https://mail.gna.org/listinfo/wesnoth-bugs
