Re: Rate limit regressions in libcurl 8.18.0 vs 8.17.0
Daniel Stenberg via curl-library <[email protected]> Sat, 3 Jan 2026 23:35:40 +0100 (CET)
| Newsgroups | gmane.comp.web.curl.library |
|---|---|
| Message-ID | <[email protected]> |
On Wed, 31 Dec 2025, Dmitry Karpov via curl-library wrote: > As I discussed it with Stefan before, the rate limit mechanism should apply > some small delay at the end of a throttled transfer to maintain the > specified rate limit for the transfer. I don't think libcurl should do that. Once the transfer is complete, I think it should return/say so. > And even though it will not save the bandwidth as all the data has been > already transferred, it will provide proper network speed measurements for > the decision making logic (i.e. bitrate selection mechanism in video > streaming apps) and will help to decrease server load in back-to-back > multi-transfer scenarios. If your app thinks it needs to add that extra wait, it is really easy for you to add a sleep there though. -- / daniel.haxx.se || https://rock-solid.curl.dev -- Unsubscribe: https://lists.haxx.se/mailman/listinfo/curl-library Etiquette: https://curl.se/mail/etiquette.html