mirror of https://github.com/moparisthebest/curl
4b86113f5e
Speed limits (from CURLOPT_MAX_RECV_SPEED_LARGE & CURLOPT_MAX_SEND_SPEED_LARGE) were applied simply by comparing limits with the cumulative average speed of the entire transfer; While this might work at times with good/constant connections, in other cases it can result to the limits simply being "ignored" for more than "short bursts" (as told in man page). Consider a download that goes on much slower than the limit for some time (because bandwidth is used elsewhere, server is slow, whatever the reason), then once things get better, curl would simply ignore the limit up until the average speed (since the beginning of the transfer) reached the limit. This could prove the limit useless to effectively avoid using the entire bandwidth (at least for quite some time). So instead, we now use a "moving starting point" as reference, and every time at least as much as the limit as been transferred, we can reset this starting point to the current position. This gets a good limiting effect that applies to the "current speed" with instant reactivity (in case of sudden speed burst). Closes #971 |
||
|---|---|---|
| .. | ||
| examples | ||
| libcurl | ||
| .gitignore | ||
| BINDINGS | ||
| BUGS | ||
| CHECKSRC.md | ||
| CODE_OF_CONDUCT.md | ||
| CODE_STYLE.md | ||
| CONTRIBUTE.md | ||
| FAQ | ||
| FEATURES | ||
| HISTORY.md | ||
| HTTP-COOKIES.md | ||
| HTTP2.md | ||
| INSTALL | ||
| INSTALL.cmake | ||
| INSTALL.devcpp | ||
| INTERNALS.md | ||
| KNOWN_BUGS | ||
| LICENSE-MIXING.md | ||
| MAIL-ETIQUETTE | ||
| MANUAL | ||
| Makefile.am | ||
| README.cmake | ||
| README.md | ||
| README.netware | ||
| README.win32 | ||
| RELEASE-PROCEDURE | ||
| RESOURCES | ||
| ROADMAP.md | ||
| SECURITY.md | ||
| SSL-PROBLEMS.md | ||
| SSLCERTS.md | ||
| THANKS | ||
| THANKS-filter | ||
| TODO | ||
| TheArtOfHttpScripting | ||
| VERSIONS | ||
| curl-config.1 | ||
| curl.1 | ||
| index.html | ||
| mk-ca-bundle.1 | ||
README.md
Documentation
You'll find a mix of various documentation in this directory and subdirectories, using several different formats. Some of them are not ideally for reading directly in your browser.
If you rather see the rendered version of the documentation, check out the curl web site's documentation section for general curl stuff or the libcurl section for libcurl related documentation.