Hmm, a port is just a way to identify a buffer in the network sub systems.
It is evem possible to have multiple apps looking at the same port at the same time, but this is highly unusuall. Examples of this are Sniffers that analyze all ports, transparantly.
For TCP/IP and UDP all you really need is the IP address and a port to connect to. The Server Listens to connections to a port and the client make connections to a remote port.
If you really want to get way to deep into TCP and the other things related like ICMP and what not, you may want to check out "UNIX Network Programming", an excelent book on the subject. Its usually a big white book with blue letters.
That book covers pretty much everything, along with example "C" source code to see how things are handled in code.
I know its UNIX, but once you understand that, then you can tackle any SOCK interface ever made real easy.
It is evem possible to have multiple apps looking at the same port at the same time, but this is highly unusuall. Examples of this are Sniffers that analyze all ports, transparantly.
For TCP/IP and UDP all you really need is the IP address and a port to connect to. The Server Listens to connections to a port and the client make connections to a remote port.
If you really want to get way to deep into TCP and the other things related like ICMP and what not, you may want to check out "UNIX Network Programming", an excelent book on the subject. Its usually a big white book with blue letters.
That book covers pretty much everything, along with example "C" source code to see how things are handled in code.
I know its UNIX, but once you understand that, then you can tackle any SOCK interface ever made real easy.