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

TCP is a stream protocol

A common mistake beginners make is assuming that any data passed into send() can be read by recv() on the other end in the same amount. In reality, sending data is similar to writing and reading from a file. If we write 10 bytes to a file, followed by another 10 bytes, then the file has 20 bytes of data. If the file is to be read later, we could read 5 bytes and 15 bytes, or we could read all 20 bytes at once, and so on. In any case, we have no way of knowing that the file was written in two 10 byte chunks.

Using send() and recv() works the same way. If you send() 20 bytes, it's not possible to tell how many recv() calls these bytes are partitioned into. It is possible that one call to recv() could return all 20 bytes, but it is also possible that a first call to recv() returns 16 bytes and that a second call to recv() is needed to...

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 €18.99/month. Cancel anytime