diff options
| author | Sandro Tosi <sandro.tosi@gmail.com> | 2012-04-23 17:45:07 (GMT) |
|---|---|---|
| committer | Sandro Tosi <sandro.tosi@gmail.com> | 2012-04-23 17:45:07 (GMT) |
| commit | cfdba61c3c51cff0e63e5cf8997a1eeb5d5f1a5a (patch) | |
| tree | b0f2411602fcf8585b81caa53150af22b2976465 /Doc/howto | |
| parent | c43125a05cc2f942ae8ba372b1dbe2e2e75d446a (diff) | |
| download | cpython-cfdba61c3c51cff0e63e5cf8997a1eeb5d5f1a5a.zip cpython-cfdba61c3c51cff0e63e5cf8997a1eeb5d5f1a5a.tar.gz cpython-cfdba61c3c51cff0e63e5cf8997a1eeb5d5f1a5a.tar.bz2 | |
Issue #14641: minor fixes to sockets Howto; patch by Dionysios Kalofonos
Diffstat (limited to 'Doc/howto')
| -rw-r--r-- | Doc/howto/sockets.rst | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/Doc/howto/sockets.rst b/Doc/howto/sockets.rst index a4ae9c0..279bb3e 100644 --- a/Doc/howto/sockets.rst +++ b/Doc/howto/sockets.rst @@ -153,7 +153,7 @@ I'm not going to talk about it here, except to warn you that you need to use there, you may wait forever for the reply, because the request may still be in your output buffer. -Now we come the major stumbling block of sockets - ``send`` and ``recv`` operate +Now we come to the major stumbling block of sockets - ``send`` and ``recv`` operate on the network buffers. They do not necessarily handle all the bytes you hand them (or expect from them), because their major focus is handling the network buffers. In general, they return when the associated network buffers have been @@ -164,7 +164,7 @@ been completely dealt with. When a ``recv`` returns 0 bytes, it means the other side has closed (or is in the process of closing) the connection. You will not receive any more data on this connection. Ever. You may be able to send data successfully; I'll talk -about that some on the next page. +more about this later. A protocol like HTTP uses a socket for only one transfer. The client sends a request, then reads a reply. That's it. The socket is discarded. This means that |