毕业设计 计算机专业外文翻译基于Socket的网络编程.docx

1、毕业设计 计算机专业外文翻译基于Socket的网络编程题 目Programming Overlay Networks with Overlay SocketsProgramming Overlay Networks with Overlay SocketsThe emergence of application-layer overlay networks has inspired the development of new network services and applications. Research on overlay net-workshas focused on the d

2、esign of protocols to maintain and forward data in an overlay network, however, less attention has been given to the software development process of building application programs in such an environment. Clearly,the complexity of overlay network protocols calls for suitable application programming in

3、terfaces (APIs) and abstractions that do not require detailed knowledge of the overlay protocol, and, thereby, simplify the task of the application programmer. In this paper, we present the concept of an overlay socket as a new programming abstraction that serves as the end point of communication in

4、 an overlay network. The overlay socket provides a socket-based API that is independent of the chosen overlay topology, and can be configured to work for different overlay topologies. The overlay socket can support application data transfer over TCP, UDP, or other transport protocols. This paper des

5、cribes the design of the overlay socket and discusses API and configuration options.1 Introduction Application-layer overlay networks 5, 9, 13, 17 provide flexible platforms for develop-ing new network services 1, 10, 11, 14, 1820 without requiring changes to the network-layer infrastructure. Member

6、s of an overlay network, which can be hosts, routers, servers, or applications, organize themselves to form a logical network topology, and commu-nicate only with their respective neighbors in the overlay topology. A member of an overlay network sends and receives application data, and also forwards

7、 data intended for other members. This paper addresses application development in overlay networks. We use the term overlay network programming to refer to the software development process of building application programs that communicate with one another in an application-layer overlay_This work is

8、 supported in part by the National Science Foundation through grant ANI-work. The diversity and complexity of building and maintaining overlay networks make it impractical to assume that application developers can be concerned with the complexity of managing the participation of an application in a

9、specific overlay networktopology. We present a software module, called overlay socket, that intends to simplify the task of overlay network programming. The design of the overlay socket pursues the following set of objectives: First, the application programming interface (API) of the overlay socket

10、does not require that an application programmer has knowledge of the overlay network topology. Second, the overlay socket is designed to accommodate dif-ferent overlay network topologies. Switching to different overlay network topologies is done by modifying parameters in a configuration file. Third

11、, the overlay socket, which operates at the applicationlayer,can accommodate different types of transport layer protocols. This is accomplished by using network adapters that interface to the un-derlying transport layer network and perform encapsulation and de-encapsulation of messages exchanged by

12、the overlay socket. Currently available network adapters are TCP, UDP, and UDP multicast. Fourth, the overlay socket provides mechanisms for bootstrapping new overlay networks. In this paper, we provide an overview of the overlay socket design and discuss over-lay network programming with the overla

13、y socket. The overlay socket has been imple-mented in Java as part of the HyperCast 2.0 software distribution 12. The software has been used for various overlay applications, and has been tested in both local-area as well as wide-area settings. The HyperCast 2.0 software implements the overlay topol

14、o-gies described in 15 and 16. This paper highlights important issues of the overlay socket, additional information can be found in the design documentation available from12. Several studies before us have addressed overlay network programming issues. Even early overlay network proposals, such as Yo

15、id 9, Scribe 4, and Scattercast 6, have presented APIs that aspire to achieve independence of the API from the overlay network topology used. Particularly, Yoid and Scattercast use a socket-like API, how-ever, these APIs do not address issues that arise when the same API is used by different overlay

16、 network topologies. Several works on application-layer multicast overlays inte-grate the application program with the software responsible for maintaining the overlay network, without explicitly providing general-purpose APIs.These include Narada 5, Overcast 13, ALMI 17, and NICE 2. A recent study 8 has proposed a common API for the class of so-called structured overlays, which includes Chord 19, CAN 18, and Bayeux 20, and