Sockets

6.1.3 Sockets

Sockets are a service provided by transport layer.
Set of primitives to enable a bi-directional comms link between A and B.

• Sockets
  • Berkeley sockets

Primitive socket commands in TCP.

1. Server side: Server startup executes SOCKET, BIND, LISTEN.
   LISTEN - allocate queue for multiple simultaneous clients.

   ACCEPT - suspend server until request. When client request arrives: ACCEPT returns.
   Start new socket (thread or process) with same properties as original, this handles the request,
   server goes on waiting on original socket.
   If new request arrives while spawning thread for this one, it is queued.
   If queue full it is refused.

2. Client side: SOCKET to create. Then CONNECT. When this returns the socket is open.

   Both sides can now SEND, RECEIVE.

   Connection not released until both sides do CLOSE. Typically client does it, server acks.

---

Ports

---

Server code in C

A simple file server in C, explained in 6.1.4:

Infinite loop. Can only be stopped by external kill (end process).
ACCEPT returns - client has connected.
Can both read from and write to the "socket address" sa.

Client sends the file name it wants.
Server writes the file to the socket and then closes the socket.
Back to infinite loop: ACCEPT - suspend waiting for next request.

Client code in C

The client for the file server:

Usage:

$ client host filename 

returns file contents to stdout.

ancientbrain.com      w2mind.org      humphrysfamilytree.com

On the Internet since 1987.      New 250 G VPS server.

Note: Links on this site to user-generated content like Wikipedia are highlighted in red as possibly unreliable. My view is that such links are highly useful but flawed.