Book Image

Hands-On Network Programming with C

By : Lewis Van Winkle
Book Image

Hands-On Network Programming with C

By: Lewis Van Winkle

Overview of this book

Network programming enables processes to communicate with each other over a computer network, but it is a complex task that requires programming with multiple libraries and protocols. With its support for third-party libraries and structured documentation, C is an ideal language to write network programs. Complete with step-by-step explanations of essential concepts and practical examples, this C network programming book begins with the fundamentals of Internet Protocol, TCP, and UDP. You’ll explore client-server and peer-to-peer models for information sharing and connectivity with remote computers. The book will also cover HTTP and HTTPS for communicating between your browser and website, and delve into hostname resolution with DNS, which is crucial to the functioning of the modern web. As you advance, you’ll gain insights into asynchronous socket programming and streams, and explore debugging and error handling. Finally, you’ll study network monitoring and implement security best practices. By the end of this book, you’ll have experience of working with client-server applications and be able to implement new network programs in C. The code in this book is compatible with the older C99 version as well as the latest C18 and C++17 standards. You’ll work with robust, reliable, and secure code that is portable across operating systems, including Winsock sockets for Windows and POSIX sockets for Linux and macOS.
Table of Contents (26 chapters)
Title Page
About Packt


Try these questions to test your knowledge acquired from this chapter:

  1. Is it ever acceptable to just terminate a program if a network error is detected?
  2. Which system functions are used to convert error codes into text descriptions?
  3. How long does it take for a call to connect() to complete on a TCP socket?
  4. What happens if you call send() on a disconnected TCP socket?
  5. How can you ensure that the next call to send() won't block?
  6. What happens if both peers to a TCP connection try to send a large amount of data simultaneously?
  7. Can you improve application performance by disabling the Nagle algorithm?
  8. How many connections can select() handle?

The answers to these questions are found in Appendix A, Answers to Questions.