Demo Data from EDBT 2026 / reviewers in the wild / expert
David L. Presotto
dblp:10/5768
· DBLP profile ↗
6ranked-venue papers
1as first author
0since 2021 · last 2008
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Software engineering, systems software and programming languages · 4 · 1 first-authorComputer networks · 1Security and privacy · 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.
| Network and information security
1 paper |
Systems and software security · 100% | |
| Software engineering, system software, and programming languages
1 paper |
Operating systems · 100% | |
| Computer architecture, parallel and distributed computing, and storage systems
1 paper |
Distributed systems · 67% Storage systems · 33% |
Topics — the 6 heaviest of 6, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Systems and software security
operating system security |
0.0 | 1 | 2002 | Security in Plan 9 · USENIX Security Symposium 2002 |
Operating systems › distributed systems
distributed operating system |
0.0 | 1 | 2002 | Security in Plan 9 · USENIX Security Symposium 2002 |
Storage systems
crash recovery |
0.0 | 1 | 1983 | PUBLISHING: A Reliable Broadcast Communication Mechanism · SOSP 1983 |
Distributed systems
fault tolerance |
0.0 | 1 | 1983 | PUBLISHING: A Reliable Broadcast Communication Mechanism · SOSP 1983 |
Distributed systems › fault tolerance › fault-tolerant protocols
reliable broadcast |
0.0 | 1 | 1983 | PUBLISHING: A Reliable Broadcast Communication Mechanism · SOSP 1983 |
Wireless networking › broadcast
broadcast network |
0.0 | 1 | 1983 | PUBLISHING: A Reliable Broadcast Communication Mechanism · SOSP 1983 |
Methods — techniques the papers use, named apart from their topics
capability-based security · 0.1message logging · 0.0
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2008 | Practical large-scale latency estimation
Michal Szymaniak, David L. Presotto, Guillaume Pierre, Maarten van Steen |
Comput. Networks | 2 |
| 2002 | Security in Plan 9
Russ Cox, Eric Grosse, Rob Pike, David L. Presotto, Sean Quinlan |
USENIX Security Symposium | 4 |
| 2001 | Protium, an Infrastructure for Partitioned ApplicationsabstractRemote access feels different from local access. The major issues are consistency (machines vary in GUIs, applications, and devices) and responsiveness (the user must wait for network and server delays), Protium attacks these by partitioning programs into local viewers that connect to remote services using application-specific protocols. Partitioning allows viewers to be customized to adapt to local features and limitations. Services are responsible for maintaining long-term state. Viewers manage the user interface and use state to reduce communication between viewer and service, reducing latency whenever possible. System infrastructure sits between the viewer and service, supporting replication, consistency, session management, and multiple simultaneous viewers. The prototype system includes an editor, a draw program, a PDF viewer, a map database, a music jukebox, and windowing system support. It runs on servers, workstations, PCs, and PDAs under Plan 9, Linux, and Windows; services and viewers have been written in C, Java, and Concurrent ML. Cliff Young, Yagati N. Lakshman, Tom Szymanski, John H. Reppy, David L. Presotto, Rob Pike, Girija J. Narlikar, Sape J. Mullender, Eric Grosse |
HotOS | 5 |
| 1990 | Interprocess Communication in the Ninth Edition Unix System
David L. Presotto, Dennis Ritchie |
Softw. Pract. Exp. | 1 |
| 1987 | DEMOS/MP: The Development of a Distributed Operating SystemabstractAbstract The DEMOS/MP operating system has moved from a supercomputer with a simple addressing structure to a network of microcomputers. This transformation was done without significant changes to the semantics of the original DEMOS, i.e. existing DEMOS programs should run on DEMOS/MP. The changes to DEMOS were simplified by the structure of its primitive objects and the functions over those objects. The structure of DEMOS links and processes were the major contributors to the simplicity. The changes made to produce DEMOS/MP involved the internal structure of link, modification to parts of the kernel, and limited changes to the various system processes. Barton P. Miller, David L. Presotto, Michael L. Powell |
Softw. Pract. Exp. | 2 |
| 1983 | PUBLISHING: A Reliable Broadcast Communication MechanismabstractPublishing is a model and mechanism for crash recovery in a distributed computing environment. Published communication works for systems connected via a broadcast medium by recording messages transmitted over the network. The recovery mechanism can be completely transparent to the failed process and all processes interacting with it. Although published communication is intended for a broadcast network such as a bus, a ring, or an Ethernet, it can be used in other environments. Michael L. Powell, David L. Presotto |
SOSP | 2 |