aboutsummaryrefslogtreecommitdiffstats
path: root/lib/public_key/doc
diff options
context:
space:
mode:
authorRory Byrne <[email protected]>2015-04-15 17:28:09 +0100
committerRory Byrne <[email protected]>2015-05-12 19:55:35 +0100
commit25bd6312491fc9153a16f74b5d1d39609426ae60 (patch)
tree0cfd7f0227302868e2b77b04b803843b87f5eb9f /lib/public_key/doc
parentce96ab6d64768cd6536011ccdecc08191c238220 (diff)
downloadotp-25bd6312491fc9153a16f74b5d1d39609426ae60.tar.gz
otp-25bd6312491fc9153a16f74b5d1d39609426ae60.tar.bz2
otp-25bd6312491fc9153a16f74b5d1d39609426ae60.zip
Fix gen_tcp:shutdown/2 by making it asynchronous
If the driver queue is empty, or the user is requesting a 'read' shutdown, then the shutdown() syscall is performed synchronously, as per the old version of shutdown/2. However, if the user is requesting a 'write' or 'read_write' shutdown, and there is data in the driver queue for the socket, then the shutdown() syscall is delayed and handled asynchronously when the driver queue is written out. This version of shutdown solves a number of issues with the old version. The two main solutions it offers are: * It doesn't block when the TCP peer is idle or slow. This is the expected behaviour when shutdown() is called: the caller needs to be able to continue reading from the socket, not be prevented from doing so. * It doesn't truncate the output. The current version of gen_tcp:shutdown/2 will truncate any outbound data in the driver queue after about 10 seconds if the TCP peer is idle of slow. Worse yet, it doesn't even inform anyone that the data has been truncated: 'ok' is returned to the caller; and a FIN rather than an RST is sent to the TCP peer. For a detailed description of all the problems with the old version of shutdown, please see the EEP Light that was written to justify this patch.
Diffstat (limited to 'lib/public_key/doc')
0 files changed, 0 insertions, 0 deletions