mirror of
https://github.com/curl/curl.git
synced 2026-07-31 11:38:06 +03:00
docs: address socket callback review feedback
This commit is contained in:
parent
21e2e54795
commit
9c58ed92c2
2 changed files with 8 additions and 10 deletions
|
|
@ -101,9 +101,7 @@ writable.
|
|||
The specified socket or file descriptor is no longer used by libcurl for any
|
||||
active transfer. It might soon be added again. After libcurl signals
|
||||
CURL_POLL_REMOVE, the application must stop monitoring that socket on
|
||||
libcurl's behalf. libcurl does not track idle connections. The pointer
|
||||
previously assigned to the socket with curl_multi_assign(3) is forgotten by
|
||||
libcurl.
|
||||
libcurl's behalf. libcurl does not track idle connections.
|
||||
|
||||
When a socket is given a CURL_POLL_REMOVE value, it might be because libcurl
|
||||
is going to close it, but it might also mean that it does not need any more
|
||||
|
|
|
|||
|
|
@ -48,16 +48,16 @@ after the easy handle has been cleaned up. The callback and data is
|
|||
inherited by a new connection and that connection may live longer
|
||||
than the transfer itself in the multi/share handle's connection cache.
|
||||
|
||||
# NOTES ON IDLE CONNECTIONS
|
||||
# NOTES ON CONNECTION REUSE
|
||||
|
||||
When using the multi interface, the close socket callback is invoked when
|
||||
libcurl closes a socket it owns. The callback and CURLOPT_CLOSESOCKETDATA(3)
|
||||
are copied from the *first* easy handle that creates the connection;
|
||||
changing this option on a subsequent easy handle that reuses the same
|
||||
connection has no effect for that connection. The callback is stored with
|
||||
the connection because the connection may outlive the easy handle that
|
||||
created it, so that libcurl can still invoke it when the connection is
|
||||
closed even after that handle has been cleaned up.
|
||||
are copied from the *first* easy handle that creates the socket used for a
|
||||
connection; changing this option on a subsequent easy handle that reuses the
|
||||
same connection has no effect for that connection. The callback is stored with
|
||||
the connection because the connection and its associated socket may outlive the
|
||||
easy handle that created it, so that libcurl can still invoke it when the
|
||||
socket is closed even after that handle has been cleaned up.
|
||||
|
||||
# DEFAULT
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue