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

Elöd Csirmaz

dblp:80/1434 · also Elöd Pal Csirmaz · DBLP profile ↗
← Back
1ranked-venue papers
0as first author
0since 2021 · last 2001
0000-0003-2449-7923ORCID · reported

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

Software engineering, systems software and programming languages · 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 · 67% Storage systems · 33%

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

TopicWeightPapersLastEvidence papers
Distributed systems › distributed coordination
conflict resolution
0.012001
An algebraic approach to file synchronization · ESEC / SIGSOFT FSE 2001
Storage systems › file systems
file synchronization
0.012001
An algebraic approach to file synchronization · ESEC / SIGSOFT FSE 2001
Distributed systems › replication
replica consistency
0.012001
An algebraic approach to file synchronization · ESEC / SIGSOFT FSE 2001

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

formal specification · 0.0algebra · 0.0
YearPublicationVenuePosition
2001 An algebraic approach to file synchronization
abstract
A file synchronizer restores consistency after multiple replicas of a filesystem have been changed independently. We present an algebra for reasoning about operations on filesystems and show that it is sound and complete with respect to a simple model. The algebra enables us to specify a file-synchronization algorithm that can be combined with several different conflict-resolution policies. By contrast, previous work builds the conflict-resolution policy into the specification, or worse, does not specify the synchronizer's behavior precisely. We classify synchronizers by asking whether conflicts can be resolved at a single disconnected replica and whether all replicas are identical after synchronization. We also discuss timestamps and argue that there is no good way to propagate timestamps when there is severe clock skew between replicas.
Norman Ramsey, Elöd Csirmaz
ESEC / SIGSOFT FSE2