Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletter Hub
Free Learning
Arrow right icon
timer SALE ENDS IN
0 Days
:
00 Hours
:
00 Minutes
:
00 Seconds
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 (26) Chapters Close

Title Page
Copyright and Credits
Dedication
About Packt Contributors Preface 1. Introducing Networks and Protocols FREE CHAPTER 2. Getting to Grips with Socket APIs 3. An In-Depth Overview of TCP Connections 4. Establishing UDP Connections 5. Hostname Resolution and DNS 6. Building a Simple Web Client 7. Building a Simple Web Server 8. Making Your Program Send Email 9. Loading Secure Web Pages with HTTPS and OpenSSL 10. Implementing a Secure Web Server 11. Establishing SSH Connections with libssh 12. Network Monitoring and Security 13. Socket Programming Tips and Pitfalls 14. Web Programming for the Internet of Things 1. Answers to Questions 2. Setting Up Your C Compiler on Windows 3. Setting Up Your C Compiler on Linux 4. Setting Up Your C Compiler on macOS 5. Example Programs 6. Other Book You May Enjoy

Chapter 2, Getting to Grips with Socket APIs

  1. What is a socket?

A socket is an abstraction that represents one endpoint of a communication link between systems.

  1. What is a connectionless protocol? What is a connection-oriented protocol?

A connection-oriented protocol sends data packets in the context of a larger stream of data. A connectionless protocol sends each packet of data independently of any before or after it.

  1. Is UDP a connectionless or connection-oriented protocol?

UDP is considered a connectionless protocol. Each message is sent independently of any before or after it.

  1. Is TCP a connectionless or connection-oriented protocol?

TCP is considered a connection-oriented protocol. Data is sent and received in order as a stream.

  1. What types of applications generally benefit from using the UDP protocol?

UDP applications benefit from better real-time performance while sacrificing reliability. They are also able to take advantage of IP multicasting.

  1. What types of applications generally benefit from using the TCP protocol?

Applications that need a reliable stream of data transfer benefit from the TCP protocol.

  1. Does TCP guarantee that data will be transmitted successfully?

TCP makes some guarantees about reliability, but nothing can truly guarantee that data is transmitted successfully. For example, if someone unplugs your modem, no protocol can overcome that.

  1. What are some of the main differences between Berkeley sockets and Winsock sockets?

The header files are different. Sockets themselves are represented as signed versus unsigned ints. When socket() or accept() calls fail, the return values are different. Berkeley sockets are also standard file descriptions. This isn't always true with Winsock. Error codes are different and retrieved in a different way. There are additional differences, but these are the main ones that affect our programs.

  1. What does the bind() function do? 

The bind() function associates a socket with a particular local network address and port number. Its usage is almost always required for the server, and it's usually not required for the client.

  1. What does the accept() function do?

The accept() function will block until a new TCP client has connected. It then returns the socket for this new connection.

  1. In a TCP connection, does the client or the server send application data first?

Either the client or the server can send data first. They can even send data simultaneously. In practice, many client-server protocols (such as HTTP) work by having the client send a request first and then having the server send a response.

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 £13.99/month. Cancel anytime
Visually different images