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

Edward A. Taft

dblp:52/147 · DBLP profile ↗
← Back
5ranked-venue papers
0as first author
0since 2021 · last 1985
—ORCID · none

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

Computer networks · 2Graphics, computer vision, multimedia, augmented reality and games · 2Systems, architecture and hardware · 1Human-computer interaction and ubiquitous computing · 1

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.

Computer architecture, parallel and distributed computing, and storage systems
1 paper
Storage systems · 91% Distributed systems · 9%
Computer networks
2 papers
Internet architecture and protocols · 73% Transport protocols and congestion control · 27%
Databases, data mining, and information retrieval
1 paper
Transaction processing and concurrency control · 100%

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

TopicWeightPapersLastEvidence papers
Storage systems
file systems
0.011985
The Alpine File System · ACM Trans. Comput. Syst. 1985
Storage systems › file systems
transactional file system
0.011985
The Alpine File System · ACM Trans. Comput. Syst. 1985
Transport protocols and congestion control › transport protocols
end-to-end protocols
0.011980
Pup: An Internetwork Architecture · IEEE Trans. Commun. 1980
Internet architecture and protocols › network architecture design
internet architecture
0.011980
Pup: An Internetwork Architecture · IEEE Trans. Commun. 1980
Internet architecture and protocols › network interconnection
internetwork protocol
0.011980
Pup: An Internetwork Architecture · IEEE Trans. Commun. 1980
Transaction processing and concurrency control
ACID transactions
0.011985
The Alpine File System · ACM Trans. Comput. Syst. 1985
Distributed systems
remote procedure call
0.011985
The Alpine File System · ACM Trans. Comput. Syst. 1985
Rendering › parallel rendering
distributed rendering
0.011974
An interactive network graphics system · SIGGRAPH 1974

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

system implementation · 0.0
YearPublicationVenuePosition
1985 The Alpine File System
abstract
Alpine is a file system that supports atomic transactions and is designed to operate as a service on a computer network. Alpine's primary purpose is to store files that represent databases. An important secondary goal is to store ordinary files representing documents, program modules, and the like. Unlike other file servers described in the literature, Alpine uses a log-based technique to implement atomic file update. Another unusual aspect of Alpine is that it performs all communication via a general-purpose remote procedure call facility. Both of these decisions have worked out well. This paper describes Alpine's design and implementation, and evaluates the system in light of our experience to date. Alpine is written in Cedar, a strongly typed modular programming language that includes garbage-collected storage. We report on using the Cedar language and programming environment to develop Alpine.
Mark R. Brown, Karen N. Kolling, Edward A. Taft
ACM Trans. Comput. Syst.3
1981 Mutual Encapsulation of Internetwork Protocols
John F. Shoch, Danny Cohen, Edward A. Taft
Comput. Networks3
1980 Pup: An Internetwork Architecture
abstract
Pup is the name of an internet packet format (PARC Universal Packet), a hierarchy of protocols, and a style of internetwork communication. The fundamental abstraction is an end-to-end media-in dependent internetwork datagram. Higher levels of functionality are achieved by end-to-end protocols that are strictly a matter of agreement among the communicating end processes. This report explores important design issues, sets forth principles that have guided the Pup design, discusses the present implementation in moderate detail, and summarizes experience with an operational internetwork. This work serves as the basis for a functioning internetwork system that provides service to about 1000 computers, on 25 networks of 5 different types, using 20 internetwork gateways.
David R. Boggs, John F. Shoch, Edward A. Taft, Robert Metcalfe
IEEE Trans. Commun.3
1975 An interactive network graphics system
Dan Cohen, Edward A. Taft
Comput. Graph.2
1974 An interactive network graphics system
abstract
This paper discusses a number of issues relevant to the design of systems for performing interactive graphics over a computer network such as the ARPA Network. We then describe a working implementation of such a system and an example of its use.
Dan Cohen, Edward A. Taft
SIGGRAPH2