Please Whitelist This Site?
I know everyone hates ads. But please understand that I am providing premium content for free that takes hundreds of hours of time to research and write. I don't want to go to a pay-only model like some sites, but when more and more people block ads, I end up working for free. And I have a family to support, just like you. :)
If you like The TCP/IP Guide, please consider the download version. It's priced very economically and you can read all of it in a convenient format without ads.
If you want to use this site for free, I'd be grateful if you could add the site to the whitelist for Adblock. To do so, just open the Adblock menu and select "Disable on tcpipguide.com". Or go to the Tools menu and select "Adblock Plus Preferences...". Then click "Add Filter..." at the bottom, and add this string: "@@||tcpipguide.com^$document". Then just click OK.
Thanks for your understanding!
Sincerely, Charles Kozierok
Author and Publisher, The TCP/IP Guide
NOTE: Using software to mass-download the site degrades the server and is prohibited.
If you want to read The TCP/IP Guide offline, please consider licensing it. Thank you.
TCP Ports, Connections and Connection Identification
(Page 2 of 2)
Multiple Connection Management
This identification of connections
using both client and server sockets is what provides the flexibility
in allowing multiple connections between devices that we take for granted
on the Internet. For example, busy application server processes (such
as Web servers) must be able to handle connections from more than one
client, or the World Wide Web would be pretty much unusable. Since the
connection is identified using the client's socket as well as the server's,
this is no problem. At the same time that the Web server maintains the
connection mentioned just above, it can easily have another connection
to say, port 2,199 at IP address 126.96.36.199. This is represented by
the connection identifier:
In fact, we can have multiple connections
from the same client to the same server. Each client process will be
assigned a different ephemeral port number, so even if they all try
to access the same server process (such as the Web server process at
188.8.131.52:80), they will all have a different client socket and represent
unique connections. This is what lets you make several simultaneous
requests to the same Web site from your computer.
Again, TCP keeps track of each of
these connections independently, so each connection is unaware of the
others. TCP can handle hundreds or even thousands of simultaneous connections.
The only limit is the capacity of the computer running TCP, and the
bandwidth of the physical connections to itthe more connections
running at once, the more each one has to share limited resources.
Key Concept: Each device can handle simultaneous TCP connections to many different processes on one or more devices. Each connection is identified by the socket numbers of the devices in the connection, called the connections endpoints. Each endpoint consists of the devices IP address and port number, so each connection is identified by the quadruple of client IP address and port number, and server IP address and port number.
|If you find The TCP/IP Guide useful, please consider making a small Paypal donation to help the site, using one of the buttons below. You can also donate a custom amount using the far right button (not less than $1 please, or PayPal gets most/all of your money!) In lieu of a larger donation, you may wish to consider purchasing a download license of The TCP/IP Guide. Thanks for your support!|
Table Of Contents - Contact Us
The TCP/IP Guide (http://www.TCPIPGuide.com)
Version 3.0 - Version Date: September 20, 2005
© Copyright 2001-2005 Charles M. Kozierok. All Rights Reserved.
Not responsible for any loss resulting from the use of this site.