Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Hands-On Network Programming with C

You're reading from   Hands-On Network Programming with C Learn socket programming in C and write secure and optimized network code

Arrow left icon
Product type Paperback
Published in May 2019
Publisher Packt
ISBN-13 9781789349863
Length 478 pages
Edition 1st Edition
Languages
Tools
Concepts
Arrow right icon
Author (1):
Arrow left icon
Lewis Van Winkle Lewis Van Winkle
Author Profile Icon Lewis Van Winkle
Lewis Van Winkle
Arrow right icon
View More author details
Toc

Table of Contents (25) Chapters Close

Preface 1. Section 1 - Getting Started with Network Programming FREE CHAPTER
2. Introducing Networks and Protocols 3. Getting to Grips with Socket APIs 4. An In-Depth Overview of TCP Connections 5. Establishing UDP Connections 6. Hostname Resolution and DNS 7. Section 2 - An Overview of Application Layer Protocols
8. Building a Simple Web Client 9. Building a Simple Web Server 10. Making Your Program Send Email 11. Section 3 - Understanding Encrypted Protocols and OpenSSL
12. Loading Secure Web Pages with HTTPS and OpenSSL 13. Implementing a Secure Web Server 14. Establishing SSH Connections with libssh 15. Section 4 - Odds and Ends
16. Network Monitoring and Security 17. Socket Programming Tips and Pitfalls 18. Web Programming for the Internet of Things 19. Answers to Questions 20. Setting Up Your C Compiler on Windows 21. Setting Up Your C Compiler on Linux 22. Setting Up Your C Compiler on macOS 23. Example Programs 24. Other Book You May Enjoy

Multiplexing TCP connections

The socket APIs are blocking by default. When you use accept() to wait for an incoming connection, your program's execution is blocked until a new incoming connection is actually available. When you use recv() to read incoming data, your program's execution blocks until new data is actually available.

In the last chapter, we built a simple TCP server. This server only accepted one connection, and it only read data from that connection once. Blocking wasn't a problem then, because our server had no other purpose than to serve its one and only client.

In the general case, though, blocking I/O can be a significant problem. Imagine that our server from Chapter 2, Getting to Grips with Socket APIs, needed to serve multiple clients. Then, imagine that one slow client connected to it. Maybe this slow client takes a minute before sending its...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime