لطفا منتظر باشید ...
Overview
Part VI of this book). To be successful as a modern developer, you have to understand how the Internet works and how to write programs that can access other computers on the Internet. Somewhere, sometime in the near future, your software will probably have to touch the Internet. Of course, desktop-style programming will not be going away, but the Internet provides such compelling connectivity that you'll probably want to use it.
In this chapter, we'll start with a primer on Transmission Control Protocol/ Internet Protocol (TCP/IP), which is used throughout the Internet, and then we'll move up one level to examine the workings of Hypertext Transfer Protocol (HTTP). Then it'll be time to get something running. We'll assemble our own intranet (a local version of the Internet) and study an HTTP client/server program based on Winsock, the fundamental API for TCP/IP. Finally, we'll move on to WinInet, which is a higher-level API than Winsock.
Internet development can be divided roughly into two types: classic Internet development and Internet development using .NET. This part of the book, Part V, looks at classic Internet development. This chapter will examine how the Internet works at the wire level. In Chapter 29, we'll look at Dynamic HTML (DHTML), which lets you apply a much more responsive feel to your Web applications. Chapter 30 will cover ATL Server—a set of templates that provide low-level C++-style access to the Internet protocols.The last part of this book, Part VI, covers .NET technology—which is the culmination of years of research and improvements with Internet development as its primary focus. The underpinnings of Internet development remain the same all over (even if you're using UNIX and Apache servers), but the amount of raw code necessary to get a Web site up and running is pretty phenomenal (as is the amount of code necessary to get a simple SDK-style window up and running). .NET offers a host of useful abstractions that hide the nitty-gritty of Web development—just as MFC and Microsoft Visual Basic .NET hide much of the complexity of the Windows API.
