TODO: 2.3 Better support for same name resolves
This commit is contained in:
parent
0d037cfdce
commit
6d79722d78
10
docs/TODO
10
docs/TODO
@ -24,6 +24,7 @@
|
|||||||
2. libcurl - multi interface
|
2. libcurl - multi interface
|
||||||
2.1 More non-blocking
|
2.1 More non-blocking
|
||||||
2.2 Fix HTTP Pipelining for PUT
|
2.2 Fix HTTP Pipelining for PUT
|
||||||
|
2.3 Better support for same name resolves
|
||||||
|
|
||||||
3. Documentation
|
3. Documentation
|
||||||
3.1 Update date and version in man pages
|
3.1 Update date and version in man pages
|
||||||
@ -221,6 +222,15 @@
|
|||||||
serial requests and currently libcurl only supports that for HEAD and GET
|
serial requests and currently libcurl only supports that for HEAD and GET
|
||||||
requests but it should also be possible for PUT.
|
requests but it should also be possible for PUT.
|
||||||
|
|
||||||
|
2.3 Better support for same name resolves
|
||||||
|
|
||||||
|
If a name resolve has been initiated for name NN and a second easy handle
|
||||||
|
wants to resolve that name as well, make it wait for the first resolve to end
|
||||||
|
up in the cache instead of doing a second separate resolve. This is
|
||||||
|
especially needed when adding many simultaneous handles using the same host
|
||||||
|
name when the DNS resolver can get flooded.
|
||||||
|
|
||||||
|
|
||||||
3. Documentation
|
3. Documentation
|
||||||
|
|
||||||
3.1 Update date and version in man pages
|
3.1 Update date and version in man pages
|
||||||
|
Loading…
x
Reference in New Issue
Block a user