TENEX, a paged time sharing system for the PDP - 10
Communications of the ACM
A system for interprocess communication in a resource sharing computer network
Communications of the ACM
A research center for augmenting human intellect
AFIPS '68 (Fall, part I) Proceedings of the December 9-11, 1968, fall joint computer conference, part I
HOST-HOST communication protocol in the ARPA network
AFIPS '70 (Spring) Proceedings of the May 5-7, 1970, spring joint computer conference
Function-oriented protocols for the ARPA computer network
AFIPS '72 (Spring) Proceedings of the May 16-18, 1972, spring joint computer conference
The augmented knowledge workshop
AFIPS '73 Proceedings of the June 4-8, 1973, national computer conference and exposition
A resource sharing executive for the ARPANET
AFIPS '73 Proceedings of the June 4-8, 1973, national computer conference and exposition
The augmented knowledge workshop
A history of personal workstations
User interface design issues for a large interactive system
AFIPS '76 Proceedings of the June 7-10, 1976, national computer conference and exposition
Elements of a distributed programming system
Computer Languages
MinimaLT: minimal-latency networking through better security
Proceedings of the 2013 ACM SIGSAC conference on Computer & communications security
Hi-index | 0.00 |
This paper proposes a high-level, application-independent framework for the construction of distributed systems within a resource sharing computer network. The framework generalizes design techniques in use within the ARPA Computer Network. It eliminates the need for application-specific communication protocols and support software, thus easing the task of the applications programmer and so encouraging the sharing of resources. The framework consists of a network-wide protocol for invoking arbitrary named functions in a remote process, and machine-dependent system software that interfaces one applications program to another via the protocol. The protocol provides mechanisms for supplying arguments to remote functions and for retrieving their results; it also defines a small number of standard data types from which all arguments and results must be modeled. The paper further proposes that remote functions be thought of as remotely callable subroutines or procedures. This model would enable the framework to more gracefully extend the local programming environment to embrace modules on other machines.