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

Bryan P. Douros

dblp:167/7027 · DBLP profile ↗
← Back
1ranked-venue papers
0as first author
0since 2021 · last 1983
—ORCID · none

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

Computer networks · 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
Distributed systems · 56% Storage systems · 44%
Software engineering, system software, and programming languages
1 paper
Operating systems · 100%

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

TopicWeightPapersLastEvidence papers
Storage systems › file systems
distributed file system
0.011983
The Architecture of an Integrated Local Network · IEEE J. Sel. Areas Commun. 1983
Operating systems › resource management › memory management › virtual memory
single-level store
0.011983
The Architecture of an Integrated Local Network · IEEE J. Sel. Areas Commun. 1983
Distributed systems › operating system support
interprocess communication
0.011983
The Architecture of an Integrated Local Network · IEEE J. Sel. Areas Commun. 1983

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

unique identifiers · 0.0layering · 0.0
YearPublicationVenuePosition
1983 The Architecture of an Integrated Local Network
abstract
The DOMAIN system is an architecture for networks of personal workstations and servers which creates an integrated distributed computing environment. Its distinctive features include: a network-wide file system of objects addressed by unique identifiers (UID's); the abstraction of a single level store for transparently accessing all objects, regardless of their location in the network; and a network-wide hierarchical name space. The implementations of these facilities exhibit several interesting approaches to layering the system software. In addition to network transparent data access, interprocess communication is provided as a basis for constructing distributed applications; as a result, we have some experience to guide the choice between these two alternative implementation techniques. Networks utilizing this architecture have been Operational for almost three years; some experience with it and lessons derived from that experience are presented, as are some performance data.
Paul J. Leach, Paul H. Levine, Bryan P. Douros, James A. Hamilton, David L. Nelson, Bernard L. Stumpf
IEEE J. Sel. Areas Commun.3