In the course of this process, the request must be transformed several times. The goal of network software is to take a request (in the form of an I/O request) from an application on one machine, pass it to another machine, execute the request on the remote machine, and return the results to the first machine. After looking at the implementation of network adapter device drivers, we examine binding, which is the glue that connects services, protocol stacks, and network adapters. You’ll learn how multiple redirector support and name resolution work, see how to access and cache remote files, and learn how a multitude of drivers interact to form a network protocol stack. Then we briefly describe the networking APIs available on Windows and explain how they are implemented. First, we present the mapping between the Windows networking software components and the Open Systems Interconnection (OSI) reference model. In this chapter, we take you from the top of the Windows networking stack to the bottom. Windows has well-defined interfaces for each layer, so in addition to using the wide variety of APIs, protocols, and network adapter device drivers that ship with Windows, third parties can extend the operating system’s networking capabilities by developing their own components. The four basic types of network software components are services, APIs, protocols, and drivers for network adapters-with each component layered on top of the next to form a network stack. Microsoft Windows was designed with networking in mind, and it includes broad networking support that is integrated with the I/O system and the Windows APIs. Windows Internals, Sixth Edition, Part 1 (2012) Chapter 7.

Windows afd socket buffer size missing