TODO: API for URL parsing/splitting
This commit is contained in:
Родитель
ca3e8268c5
Коммит
546d4a3505
|
@ -36,6 +36,7 @@
|
|||
1.18 try next proxy if one doesn't work
|
||||
1.19 Timeout idle connections from the pool
|
||||
1.20 SRV and URI DNS records
|
||||
1.21 API for URL parsing/splitting
|
||||
1.22 Monitor connections in the connection pool
|
||||
1.23 Offer API to flush the connection pool
|
||||
|
||||
|
@ -353,6 +354,13 @@
|
|||
Offer support for resolving SRV and URI DNS records for libcurl to know which
|
||||
server to connect to for various protocols (including HTTP!).
|
||||
|
||||
1.21 API for URL parsing/splitting
|
||||
|
||||
libcurl has always parsed URLs internally and never exposed any API or
|
||||
features to allow applications to do it. Still most or many applications
|
||||
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.
|
||||
|
||||
1.22 Monitor connections in the connection pool
|
||||
|
||||
If the server sends HTTP/2 frames (like for example an HTTP/2 PING frame) to
|
||||
|
|
Загрузка…
Ссылка в новой задаче