mirror of
https://github.com/moparisthebest/curl
synced 2024-08-13 17:03:50 -04:00
TODO: remove the 1.22 duplicated item
This commit is contained in:
parent
4e1ebe63cf
commit
63cc406389
15
docs/TODO
15
docs/TODO
@ -29,14 +29,13 @@
|
|||||||
1.11 minimize dependencies with dynamicly loaded modules
|
1.11 minimize dependencies with dynamicly loaded modules
|
||||||
1.12 have form functions use CURL handle argument
|
1.12 have form functions use CURL handle argument
|
||||||
1.14 Typesafe curl_easy_setopt()
|
1.14 Typesafe curl_easy_setopt()
|
||||||
1.15 TCP Fast Open
|
1.15 Monitor connections in the connection pool
|
||||||
1.16 Try to URL encode given URL
|
1.16 Try to URL encode given URL
|
||||||
1.17 Add support for IRIs
|
1.17 Add support for IRIs
|
||||||
1.18 try next proxy if one doesn't work
|
1.18 try next proxy if one doesn't work
|
||||||
1.19 Timeout idle connections from the pool
|
1.19 Timeout idle connections from the pool
|
||||||
1.20 SRV and URI DNS records
|
1.20 SRV and URI DNS records
|
||||||
1.21 API for URL parsing/splitting
|
1.21 API for URL parsing/splitting
|
||||||
1.22 Monitor connections in the connection pool
|
|
||||||
1.23 Offer API to flush the connection pool
|
1.23 Offer API to flush the connection pool
|
||||||
|
|
||||||
2. libcurl - multi interface
|
2. libcurl - multi interface
|
||||||
@ -351,18 +350,6 @@
|
|||||||
using libcurl need that ability. In polls to users, we've learned that many
|
using libcurl need that ability. In polls to users, we've learned that many
|
||||||
libcurl users would like to see and use such an API.
|
libcurl users would like to see and use such an API.
|
||||||
|
|
||||||
1.22 Monitor connections in the connection pool
|
|
||||||
|
|
||||||
If the server sends HTTP/2 frames (like for example an HTTP/2 PING frame) to
|
|
||||||
curl while the connection is held in curl's connection pool, the socket will
|
|
||||||
be found readable when considered for reuse and that makes curl think it is
|
|
||||||
dead and then it will be closed and a new connection gets created instead.
|
|
||||||
|
|
||||||
This is *best* fixed by adding monitoring to connections while they are kept
|
|
||||||
in the pool so that pings can be responded to appropriately. It would also
|
|
||||||
proper allow libcurl to close connections (earlier) when they are closed by
|
|
||||||
the server. Also, see "1.19 Timeout idle connections from the pool"
|
|
||||||
|
|
||||||
1.23 Offer API to flush the connection pool
|
1.23 Offer API to flush the connection pool
|
||||||
|
|
||||||
Sometimes applications want to flush all the existing connections kept alive.
|
Sometimes applications want to flush all the existing connections kept alive.
|
||||||
|
Loading…
Reference in New Issue
Block a user