Showing papers on "Shared resource published in 1973"

Computer-communication networks

Abstract: In 1968 the Advanced Research Projects Agency (ARPA) of the U.S. Department of Defense began implementation of a computer communication network which permits the interconnection of heter ogeneous computers at geographically distributed centres through out the United States. This network has come to be known as the ARPANET and has grown from the initial four node configuration in 1969 to almost forty nodes (including satellite nodes in Hawaii, Norway, and London) in late 1973. The major goal of ARPANET is to achieve resource sharing among the network users. The resources to be shared include not only programs, but also unique facilities such as the powerful ILLIAC IV computer and large global weather data bases that are economically feasible when widely shared. The ARPANEr employs a distributed store-and-forward packet switching approach that is much better suited for computer communications networks than the more conventional circuit-switch ing approach. Reasons favouring packet switching include lower cost, higher capacity, greater reliability and minimal delay. All of these factors are discussed in these Proceedings."

A resource sharing executive for the ARPANET

Abstract: The Resource Sharing Executive (RSEXEC) is a distributed, executive-like system that runs on TENEX Host computers in the ARPA computer network. The RSEXEC creates an environment which facilitates the sharing of resources among Hosts on the ARPANET. The large Hosts, by making a small amount of their resources available to small Hosts, can help the smaller Hosts provide services which would otherwise exceed their limited capacity. By sharing resources among themselves the large Hosts can provide a level of service better than any one of them could provide individually. Within the environment provided by the RSEXEC a user need not concern himself directly with network details such as communication protocols nor even be aware that he is dealing with a network.

Wholesale/retail specification in resource sharing networks

Abstract: Technical feasibility of computer-communication networks has already been demonstrated [3, 5, 8, 14] for general purpose computers, and evidence is currently being presented to show that economic viability is also feasible. [8, 14]

A loop network for general purpose data communications in a heterogeneous world

Abstract: How do you interconnect a large, heterogeneous group of computers, batch terminals and conversational terminals to form a general purpose network of computing resources? What techniques and technologies can be applied to maximize throughput and minimize response times? Is major surgery on host processor operating systems really necessary to interface to a communications network?This paper will describe a packet switching data communications network under development at the National Security Agency for resource sharing and the future development of distributed processing and filing systems. Starting with an experimental three node loop, the network will consist of a hierarchy of interconnected loops or rings probably based on Bell System T carrier digital transmission technology.Also discussed will be the means of nodal connection to the loops, the configuration of a node, network protocol, security considerations and implications for the future.

VIEW: A Distributed System for Graphical Analysis of Large Data Bases.

Abstract: : Research projects using large numerical simulations of natural phenomena encounter problems acquiring computer and data storage resources. Work by the ARPA-sponsored climate project at Rand is cited as exemplifying these problems. Certain of these problems are solvable by the large-scale resource sharing of the ARPA Network. The VIEW system addresses a further problem -- aiding researchers via graphical analysis of large, remotely-located data bases. In order to access remote data storage facilities (e.g., the trillion-bit Laser Store), modules of VIEW are distributed over the ARPA network, with the main analysis module on the UCLA 360/91. The user/system interface was designed to satisfy a set of user-generated specifications and to allow syntactically different inputs to remote data retrieval systems. Terminal input/output is in a Network standard format, allowing use of VIEW from any graphics terminal connected to the Network.