TCP / HTTP Listening On Ports: How Can Many Users Share the Same Port So, what happens when a server listen for incoming connections on a TCP port? For example, let’s say you have a web-server on port 80. Let’s assume that your computer has the public IP address of 24.14.181.229 and the person that … Read more
What about SCTP. It’s a standard protocol by the IETF (RFC 4960) It has chunking capability which could help for speed. Update: a comparison between TCP and SCTP shows that the performances are comparable unless two interfaces can be used. Update: a nice introductory article.
For my suggestion, please read the last section: “When to use SO_LINGER with timeout 0”. Before we come to that a little lecture about: Normal TCP termination TIME_WAIT FIN, ACK and RST Normal TCP termination The normal TCP termination sequence looks like this (simplified): We have two peers: A and B A calls close() A … Read more
The answer differs depending on what OS is being considered. In general though: For TCP, no. You can only have one application listening on the same port at one time. Now if you had 2 network cards, you could have one application listen on the first IP and the second one on the second IP … Read more
It’s fatal. The remote server has sent you a RST packet, which indicates an immediate dropping of the connection, rather than the usual handshake. This bypasses the normal half-closed state transition. I like this description: “Connection reset by peer” is the TCP/IP equivalent of slamming the phone back on the hook. It’s more polite than … Read more