Cache Coherence and Storage Management in a Persistent Object System

B Koch; T Schunke; Alan Dearle; F Vaughan; C Marlin; Ruth Fazakerley; C Barter

Cache Coherence and Storage Management in a Persistent Object System

B Koch, T Schunke, Alan Dearle, F Vaughan, C Marlin, Ruth Fazakerley, C Barter

School of Computer Science

Research output: Chapter in Book/Report/Conference proceeding › Conference contribution

Abstract

A distributed architecture for the support of programs written in the persistent programming language Napier is described. The architecture consists of a central server containing the stable persistent store and a collection of clients, each executing Napier processes. Since each client has a cache of objects, some of which may be shared with other clients, a protocol is required to ensure that the caches are coherent and that any access of an object will be to the most up-to- date copy. This architecture is explicated by following the lifecycle of an object from its ‘birth’ inside a client, through its life in the persistent store and its migration into other clients. Using this vehicle, the coherency protocol and client/server architecture are illustrated and explained.

Original language	English
Title of host publication	Proceedings of the 4th International Workshop on Persistent Object Systems (POS4)
Subtitle of host publication	Implementing Persistent Object Bases
Editors	A Dearle, G Shaw, SB Zdonik
Publisher	Morgan Kaufmann
Pages	103-113
ISBN (Print)	1-55860-168-6
Publication status	Published - 1990

Cite this

@inproceedings{fd0b06417b0d4a919f6a356880579716,

title = "Cache Coherence and Storage Management in a Persistent Object System",

abstract = "A distributed architecture for the support of programs written in the persistent programming language Napier is described. The architecture consists of a central server containing the stable persistent store and a collection of clients, each executing Napier processes. Since each client has a cache of objects, some of which may be shared with other clients, a protocol is required to ensure that the caches are coherent and that any access of an object will be to the most up-to- date copy. This architecture is explicated by following the lifecycle of an object from its {\textquoteleft}birth{\textquoteright} inside a client, through its life in the persistent store and its migration into other clients. Using this vehicle, the coherency protocol and client/server architecture are illustrated and explained.",

author = "B Koch and T Schunke and Alan Dearle and F Vaughan and C Marlin and Ruth Fazakerley and C Barter",

year = "1990",

language = "English",

isbn = "1-55860-168-6",

pages = "103--113",

editor = "A Dearle and G Shaw and SB Zdonik",

booktitle = "Proceedings of the 4th International Workshop on Persistent Object Systems (POS4)",

publisher = "Morgan Kaufmann",

}

Cache Coherence and Storage Management in a Persistent Object System. / Koch, B; Schunke, T; Dearle, Alan et al.
Proceedings of the 4th International Workshop on Persistent Object Systems (POS4): Implementing Persistent Object Bases. ed. / A Dearle; G Shaw; SB Zdonik. Morgan Kaufmann, 1990. p. 103-113.

Research output: Chapter in Book/Report/Conference proceeding › Conference contribution

TY - GEN

T1 - Cache Coherence and Storage Management in a Persistent Object System

AU - Koch, B

AU - Schunke, T

AU - Dearle, Alan

AU - Vaughan, F

AU - Marlin, C

AU - Fazakerley, Ruth

AU - Barter, C

PY - 1990

Y1 - 1990

N2 - A distributed architecture for the support of programs written in the persistent programming language Napier is described. The architecture consists of a central server containing the stable persistent store and a collection of clients, each executing Napier processes. Since each client has a cache of objects, some of which may be shared with other clients, a protocol is required to ensure that the caches are coherent and that any access of an object will be to the most up-to- date copy. This architecture is explicated by following the lifecycle of an object from its ‘birth’ inside a client, through its life in the persistent store and its migration into other clients. Using this vehicle, the coherency protocol and client/server architecture are illustrated and explained.

AB - A distributed architecture for the support of programs written in the persistent programming language Napier is described. The architecture consists of a central server containing the stable persistent store and a collection of clients, each executing Napier processes. Since each client has a cache of objects, some of which may be shared with other clients, a protocol is required to ensure that the caches are coherent and that any access of an object will be to the most up-to- date copy. This architecture is explicated by following the lifecycle of an object from its ‘birth’ inside a client, through its life in the persistent store and its migration into other clients. Using this vehicle, the coherency protocol and client/server architecture are illustrated and explained.

UR - https://archive.cs.st-andrews.ac.uk/papers/download/KSD+90.pdf

M3 - Conference contribution

SN - 1-55860-168-6

SP - 103

EP - 113

BT - Proceedings of the 4th International Workshop on Persistent Object Systems (POS4)

A2 - Dearle, A

A2 - Shaw, G

A2 - Zdonik, SB

PB - Morgan Kaufmann

ER -

Cache Coherence and Storage Management in a Persistent Object System

Abstract

Other files and links

Fingerprint

Cite this