Introduction to TCP/IP and Sockets, part 2: Example code Walk-Through

This is a walk-through of example C++ code for using Sockets to send and receive messages between programs using the Internet protocols.

This is part 2 of the series. Part 1 is here:    • Introduction to TCP/IP and Sockets, part 1...  

Here is a link to all the code: https://github.com/rhymu8354/SocketTu...

Index for skipping to the sections you care about:

00:00 - Introduction
01:55 - Downloading the tutorial/example code
02:28 - Opening and building in VSCode
03:52 - Running the TCP server example
04:24 - Modifying TCP client example to run it to connect to TCP server
05:16 - Running the TCP client example
05:38 - Showing TCP client/server exchange using WireShark
09:28 - Running the UDP receiver example
09:49 - Running the UDP sender example (after setting correct IP address)
11:27 - Showing UDP sender/receiver exchange using WireShark
12:15 - Code walk-through begins
12:45 - Sender program (UDP)
13:41 - Receiver program (UDP)
15:16 - DatagramSocket class (UDP, shared by Sender and Receiver programs)
22:50 - Explanation of the 3 common results from socket I/O
25:02 - Differences between POSIX Sockets and WinSock
27:45 - Usage of mutexes to allow asynchronous operations to be thread-safe
28:47 - Rule about not holding mutexes when calling callbacks (to avoid deadlocks)
29:59 - Warning to not assume that it's still safe to access the same state after releasing and then reacquiring a mutex
30:43 - General coding pattern: Pimpl (pointer to implementation)
31:19 - General coding pattern: C++ rule of zero/three/five
33:07 - Client program (TCP)
35:26 - Server program (TCP)
39:03 - Callbacks for when data is received or the connection is closed
40:58 - ClientSocket class (TCP, used by Client program)
43:40 - ServerSocket class (TCP, used by Server program)
47:28 - ServerSocket::Client class (client-server state object)
47:53 - Connection class (TCP, shared by ClientSocket and ServerSocket)
53:25 - O/S abstractions: UsesSockets (WinSock startup/cleanup helper)
54:52 - O/S abstractions: SocketEventLoop (asynchronous socket I/O)

If you would like to see more information on setting up CMake and C/C++ to work with VSCode, this video covers these topics in more detail:    • Introduction to Google Test and CMake