Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data. A simulation from public publication records: the people listed were not invited and did not agree to review.
? Tutorial for this page

Titus D. M. Purdin

dblp:12/6482 · DBLP profile ↗
← Back
3ranked-venue papers
1as first author
0since 2021 · last 1988
—ORCID · none

Domains — the database's venue-derived domains; a paper can count in several

Software engineering, systems software and programming languages · 3 · 1 first-author

Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.

Software engineering, system software, and programming languages
2 papers
Operating systems · 64% Programming languages and type systems · 36%
Computer architecture, parallel and distributed computing, and storage systems
2 papers
Distributed systems · 57% Storage systems · 43%

Topics — the 6 heaviest of 6, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Programming languages and type systems
distributed programming languages
0.011988
An Overview of the SR Language and Implementation · ACM Trans. Program. Lang. Syst. 1988
Operating systems › distributed systems
distributed operating system
0.011987
The Design of the Saguaro Distributed Operating System · IEEE Trans. Software Eng. 1987
Operating systems
interprocess communication
0.011987
The Design of the Saguaro Distributed Operating System · IEEE Trans. Software Eng. 1987
Distributed systems › distributed resource management
distributed resource allocation
0.011987
The Design of the Saguaro Distributed Operating System · IEEE Trans. Software Eng. 1987
Storage systems › file systems › distributed file system
file replication
0.011987
The Design of the Saguaro Distributed Operating System · IEEE Trans. Software Eng. 1987
Distributed systems
distributed programming
0.011988
An Overview of the SR Language and Implementation · ACM Trans. Program. Lang. Syst. 1988

Methods — techniques the papers use, named apart from their topics

semaphores · 0.0rendez-vous · 0.0remote procedure call · 0.0multicast · 0.0asynchronous message passing · 0.0type system · 0.0
YearPublicationVenuePosition
1988 An Overview of the SR Language and Implementation
abstract
SR is a language for programming distributed systems ranging from operating systems to application programs. On the basis of our experience with the initial version, the language has evolved considerably. In this paper we describe the current version of SR and give an overview of its implementation. The main language constructs are still resources and operations. Resources encapsulate processes and variables that they share; operations provide the primary mechanism for process interaction. One way in which SR has changed is that both resources and processes are now created dynamically. Another change is that inheritance is supported. A third change is that the mechanisms for operation invocation—call and send—and operation implementation—proc and in—have been extended and integrated. Consequently, all of local and remote procedure call, rendezvous, dynamic process creation, asynchronous message passing, multicast, and semaphores are supported. We have found this flexibility to be very useful for distributed programming. Moreover, by basing SR on a small number of well-integrated concepts, the language has proved easy to learn and use, and it has a reasonably efficient implementation.
Gregory R. Andrews, Ronald A. Olsson, Michael H. Coffin, Irving Elshoff, Kelvin D. Nilsen, Titus D. M. Purdin, Gregg M. Townsend
ACM Trans. Program. Lang. Syst.6
1987 A File Replication Facility for Berkeley Unix
abstract
Abstract This paper describes two mechanisms – reproduction sets and metafiles – that provide low‐cost, semi‐automatic file replication and location transparency facilities for an interconnected collection of machines running Berkeley Unix. A reproduction set is a collection of files that the system attempts to keep identical; this is done on a ‘best effort’ basis, with the system relying on the user to handle unusual situations. A metafile is a special file that contains symbolic pathnames of other files, each of which may be on any machine in the network; opening a metafile results in opening an available constituent file. Examples are given to illustrate the use of these mechanisms. Their implementation and performance are also described.
Titus D. M. Purdin, Richard D. Schlichting, Gregory R. Andrews
Softw. Pract. Exp.1
1987 The Design of the Saguaro Distributed Operating System
abstract
This paper describes the design of the Saguaro operating system for computers connected by a local-area network. Systems constructed on such an architecture have the potential advantages of concurrency and robustness. In Saguaro, these advantages are made available to the user through several mechanisms. One is channels, an interprocess communication and synchronization facility that allows the input and output of different commands to be connected to form general graphs of communicating processes. Two additional mechanisms are provided to support semitransparent file replication and access: reproduction sets and metafiles. A reproduction set is a collection of files that the system attempts to keep identical on a "best effort" basis. A metafile is a special file that contains symbolic pathnames of other files; when a metafile is opened, the system selects an available constituent file and opens it instead. The advantages of concurrency and robustness are also realized at the system level by the use of pools of server processes and decentralized allocation protocols. Saguaro also makes extensive use of a type system to describe user data such as files and to specify the types of arguments to commands and procedures. This enables the system to assist in type checking and leads to a user interface in which command-specific templates are available to facilitate command invocation.
Gregory R. Andrews, Richard D. Schlichting, Roger Hayes, Titus D. M. Purdin
IEEE Trans. Software Eng.4