【正文】 畢業(yè)設(shè)計 (論文 )外文文獻翻譯 譯文一 ： Introduction to TCP/IP – Introduction 譯文二 ： Client Server Programming with Winsock 學(xué)生姓名 學(xué) 號 系 別 信息與電子系 專業(yè) 班級 計算機科學(xué)與技術(shù) Introduction to TCP/IP– Introduction Author Catalyst Development Catalyst Development is a recognized leader in Inter ponent software whose awardwinning products are used by thousands of corporate, government and independent developers around the world. Introduction With the acceptance of TCP/IP as a standard platformindependent work protocol, and the explosive growth of the Inter, the Windows Sockets API (application program interface) has emerged as the standard for work programming in the Windows environment. This document will introduce the basic concepts behind Windows Sockets programming and get you started with your first application created with SocketWrench. SocketWrench is part of a package developed by Catalyst called the SocketTools Visual Edition. SocketTools includes ponents and libraries for many of the popular Inter application protocols, such as FTP, POP3, SMTP and HTTP. For more information about the plete SocketTools package, visit the Catalyst website at . It is assumed that the reader is familiar with Visual Basic and has installed the SocketWrench you39。re already familiar with sockets programming, feel free to skip this section. There are two general approaches that you can take when creating a program that uses Windows Sockets. One is to code directly against the API. The other is to use a ponent which provides a higherlevel interface to the library by setting properties and responding to events. This can provide a more natural programming interface, and it allows you to avoid much of the errorprone drudgery monly associated with sockets programming. By including the control in a project, setting some properties and responding to events, you can quickly and easily write an Interenabled application. SocketWrench provides a prehensive interface to the Windows Sockets library and will be used to build a simple clientserver application in the next section of this document. Before we get started with the control, however, we39。ll cover the basic terminology and concepts behind sockets programming in general. Transmission Control Protocol (TCP) When two puters wish to exchange information over a work, there are several ponents that must be in place before the data can actually be sent and received. Of course, the physical hardware must exist, which is typically either a work interface card (NIC) or a serial munications port for dialup working connections. Beyond this physical connection, however, puters also need to use a protocol which defines the parameters of the munication between them. In short, a protocol defines the rules of the road that each puter must follow so that all of the systems in the work can exchange data. One of the most popular protocols in use today is TCP/IP, which stands for Transmission Control Protocol/Inter Protocol. By convention, TCP/IP is used to refer to a suite of protocols, all based on the Inter Protocol (IP). Unlike a single local work, where every system is directly connected to each other, an inter is a collection of works, bined into a single, virtual work. The Inter Protocol provides the means by which any system on any work can municate with another as easily as if they were on the same physical work. Each system, monly referred to as a host, is assigned a unique 32bit number which can be used to identify it over the work. Typically, this address is broken into four 8bit numbers separated by periods. This is called dotnotation, and looks something like . Some parts of the address are used to identify the work that the system is connected to, and the remainder identifies the system itself. Without going into the minutia of the Inter addressing scheme, just be aware that there are three classes of addresses, referred to as A, B and C. The rule of thumb is that class A addresses are assigned to very large works, class B addresses are assigned to medium sized works, and class C addresses a