@InProceedings{carey:shore,
  author = {Michael J. Carey and David J. DeWitt and Michael J. Franklin and
  Nancy E. Hall and Mark L. McAuliffe and Jeffrey F. Naughton and Daniel T.
  Schuh and Marvin H. Solomon and C. K. Tan and Odysseas G. Tsatalos and Seth
  J. White and Michael J. Zwilling},
  title = {Shoring Up Persistent Applications},
  booktitle = {Proceedings of the ACM SIGMOD International Conference on
  Management of Data},
  year = {1994},
  pages = {383--394},
  publisher = {ACM Press},
  keywords = {persistent systems, database, parallel I/O, object-oriented,
  pario-bib},
  comment = {SHORE is a persistent object database system. It is intended for
  parallel or distributed systems, and attempts to combine both DB and file
  system features. Everything in the database is a typed object, in that there
  is a registered interface object that defines this type, including the basic
  data types of elements of the object, and methods that manipulate the object.
  Every object has an OID, and objects can refer to other objects with the OID.
  But they also support unix-like namespace, in which the names refer to
  objects by giving the OID. They also have a unix-compatibility library that
  provides access to many objects through the unix file interface. Every node
  has a SHORE server, and applications talk to their local server for all their
  needs. The local server talks to other servers as needed. The servers are
  also responsible for caching pages and managing locks and transactions.}
}