Proceedings 21st International Conference on Distributed Computing Systems
DOI: 10.1109/icdsc.2001.918975
|View full text |Cite
|
Sign up to set email alerts
|

Fast reconciliations in fluid replication

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
12
0

Publication Types

Select...
3
2
2

Relationship

0
7

Authors

Journals

citations
Cited by 19 publications
(12 citation statements)
references
References 17 publications
0
12
0
Order By: Relevance
“…In step (6), all the mandatory replicas are added to R, because a mandatory replica has at least one replica that is not included in the range originators of any classified replicas.…”
Section: Calculation Of a Minimum Readmentioning
confidence: 99%
“…In step (6), all the mandatory replicas are added to R, because a mandatory replica has at least one replica that is not included in the range originators of any classified replicas.…”
Section: Calculation Of a Minimum Readmentioning
confidence: 99%
“…In Fluid Replication [7], clients can create replicas dynamically, whenever and wherever they are necessary. When a client sees that performance is low, either because of increasing demand on the network, or because of client mobility, he can create replicas on a waystation, which is a node on which replicas can be created.…”
Section: Related Workmentioning
confidence: 99%
“…Update Ordering Constraints: When updates are issued independently at multiple replicas (e.g., by 'WR' mode sessions), our model allows them to be applied (1) with no particular constraint on their ordering at various replicas (called 'none'), (2) in some arbitrary but common order everywhere (called 'total'), or (3) sequentially via serialization (called 'serial'). The ordering options can be specified on a per-session basis.…”
Section: Composable Consistency Modelmentioning
confidence: 99%
“…Several P2P systems were developed to share read-only data such as multimedia files (PAST [13], KaZaa) or access to rarely write-shared personal files [14], but not frequent write-sharing. Numerous consistency schemes have been developed individually to handle the data coherence needs of specific services such as file systems, directory services [9], databases and persistent object systems [8] [2] provides multiple selectable consistency policies for static hierarchical caching. In contrast, our approach offers primitive options that can be combined to yield a variety of policies, offering more customizability for peer-to-peer replication.…”
Section: Related Workmentioning
confidence: 99%