HTTP/2 supports queries multiplexing, headers compression, priority and more intelligent packet streaming management. This results in reduced latency and accelerates content download on modern web pages. More details here.
netem leverages functionality already built into Linux and userspace utilities to simulate networks. This is actually what Mark’s answer refers to, by a different name. The examples on their homepage already show how you can achieve what you’ve asked for: Examples Emulating wide area network delays This is the simplest example, it just adds a … Read more
A single listening port can accept more than one connection simultaneously. There is a ’64K’ limit that is often cited, but that is per client per server port, and needs clarifying. Each TCP/IP packet has basically four fields for addressing. These are: source_ip source_port destination_ip destination_port <—– client ——> <——— server ————> Inside the TCP … Read more
This is one of my favorite questions. UDP is so misunderstood. In situations where you really want to get a simple answer to another server quickly, UDP works best. In general, you want the answer to be in one response packet, and you are prepared to implement your own protocol for reliability or to resend. … 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
As pointed by B. Rhodes, nc (netcat) will do the job. A more compact way to use it: nc -z <host> <port> That way nc will only check if the port is open, exiting with 0 on success, 1 on failure. For a quick interactive check (with a 5 seconds timeout): nc -z -v -w5 … Read more
Connect to a non-routable IP address, such as 10.255.255.1.
You might have guessed it already: it’s a connection error. “ECONNRESET” means the other side of the TCP conversation abruptly closed its end of the connection. This is most probably due to one or more application protocol errors. You could look at the API server logs to see if it complains about something. But since … Read more
The port number is an unsigned 16-bit integer, so 65535.
First off, a “port” is just a number. All a “connection to a port” really represents is a packet which has that number specified in its “destination port” header field. Now, there are two answers to your question, one for stateful protocols and one for stateless protocols. For a stateless protocol (ie UDP), there is … Read more