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.

Joost Verhofstad

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

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

Databases, data management, data science and information retrieval · 1 · 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.

Computer architecture, parallel and distributed computing, and storage systems
1 paper
Storage systems · 100%
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
crash resistance
0.011977
Recovery and Carsh Resistance in a Filing System · SIGMOD Conference 1977
Storage systems › file systems
file system recovery
0.011977
Recovery and Carsh Resistance in a Filing System · SIGMOD Conference 1977
Storage systems › storage reliability
file system reliability
0.011977
Recovery and Carsh Resistance in a Filing System · SIGMOD Conference 1977

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

undo/redo · 0.0checkpointing · 0.0
YearPublicationVenuePosition
1977 Recovery and Carsh Resistance in a Filing System
abstract
This paper describes mechanisms that provide the user of a filing system the dynamic facility for defining a scope within which backing out can be done on request.Check points (defining the beginning of a new scope) can dynamically be established and procedures for 'acceptance' (at the end of the scope) or 'undoing' (within or at the end of the scope) can be invoked. These scopes can be nested.It is also shown that these mechanisms can be used to provide crash resistance. After a crash the system will be left in the state it was in before it entered the current scope (or outermost scope if scopes are nested).
Joost Verhofstad
SIGMOD Conference1