The Cambridge File Server

Dion, Jeremy

doi:10.1145/850708.850710

Cited by 55 publications

(9 citation statements)

References 3 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In some distributed systems, such as the Cambridge File Server [Dion 1980] and the LOCUS system [Popek et al 1981], the identifiers of files (the objects of the systems) are structured, where pan of the structure captures an aspect of the location of the object, such as a disk or server. For example, in LOCUS part of the identifier of a file identifies a (logical) volume where the file is located.…”

Section: Identity Through Structured Identifiermentioning

confidence: 99%

Object identity

Khoshafian¹,

Copeland²

1986

Conference Proceedings on Object-Oriented Programming Systems, Languages and Applications - OOPLSA '86

231

View full text Add to dashboard Cite

Identity is that property of an object which distinguishes each object from all others. Identity has been investigated almost independently in general-purpose programming languages and database languages. Its importance is growing as these two environments evolve and merge.We describe a continuum between weak and strong support of identity, and argue for the incorporation of the strong notion of identity at the conceptual level in languages for general purpose programming, database systems and their hybrids. We define a data model that can directly describe complex objects, and show that identity can easily be incorporated in it.Finally, we compare d~erent implementation schemes for identity and argue that a surrogate-based implementation scheme is needed to support the strong notion of identity.

show abstract

Section: Identity Through Structured Identifiermentioning

confidence: 99%

Object identity

Khoshafian¹,

Copeland²

1986

Conference Proceedings on Object-Oriented Programming Systems, Languages and Applications - OOPLSA '86

231

View full text Add to dashboard Cite

show abstract

“…For example, Dion quotes access times of 50 ms to read 512 bytes and 65 ms to write 512 bytes. 6 Networking In addition to LAN-wide access, Helix supports access to objects on file servers in remote local area networks.…”

Section: Resource Managementmentioning

confidence: 99%

Helix: The Architecture of the XMS Distributed File system

Fridrich¹,

Older²

1985

IEEE Softw.

View full text Add to dashboard Cite

“…They all have mechanisms for concurrency control. Most file servers, including the Cambridge File Server [Dion80], XDFS, FELIX and ALPINE use locking [Eswaran76], while some, among them SWALLOW, use timestamps [Reed78].…”

Section: Related Workmentioning

confidence: 99%

A distributed file service based on optimistic concurrency control

Mullender¹,

Tanenbaum

1985

SIGOPS Oper. Syst. Rev.

View full text Add to dashboard Cite

The design of a layered file service for the Amoeba Distributed System is discussed, on top of which various applications can easily be intplemented. The bottom layer is formed by the Amoeba Block Services, responsible for implementing stable storage and repficated, highly available disk blocks. The next layer is formed by the Amoeba File Service which provides version management and concur~ncy control for tree-structured files. On top of this layer, the appficafions, ranging from databases to source code control systems, determine the structure of the file trees and provide an interface to the users.

show abstract

The Cambridge File Server

Cited by 55 publications

References 3 publications

Object identity

Object identity

Helix: The Architecture of the XMS Distributed File system

A distributed file service based on optimistic concurrency control

Contact Info

Product

Resources

About