diff options
| author | Daniel Stenberg <daniel@haxx.se> | 2017-06-08 08:34:32 +0200 |
|---|---|---|
| committer | Daniel Stenberg <daniel@haxx.se> | 2017-06-08 10:50:47 +0200 |
| commit | 7fffe97b787b962fc0afcd5737cec411f2bc0023 (patch) | |
| tree | 7d184eea0449a79a51bd2367c9b4da96228a98f4 /lib/speedcheck.c | |
| parent | 165b7f50991277699fc7dc4758ec7f501372a75a (diff) | |
expire: remove Curl_expire_latest()
With the introduction of expire IDs and the fact that existing timers
can be removed now and thus never expire, the concept with adding a
"latest" timer is not working anymore as it risks to not expire at all.
So, to be certain the timers actually are in line and will expire, the
plain Curl_expire() needs to be used. The _latest() function was added
as a sort of shortcut in the past that's quite simply not necessary
anymore.
Follow-up to 31b39c40cf90
Reported-by: Paul Harris
Closes #1555
Diffstat (limited to 'lib/speedcheck.c')
| -rw-r--r-- | lib/speedcheck.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/lib/speedcheck.c b/lib/speedcheck.c index 694d7f695..8addedde5 100644 --- a/lib/speedcheck.c +++ b/lib/speedcheck.c @@ -67,7 +67,7 @@ CURLcode Curl_speedcheck(struct Curl_easy *data, if(data->set.low_speed_limit) /* if low speed limit is enabled, set the expire timer to make this connection's speed get checked again in a second */ - Curl_expire_latest(data, 1000, EXPIRE_SPEEDCHECK); + Curl_expire(data, 1000, EXPIRE_SPEEDCHECK); return CURLE_OK; } |