• DocumentCode
    3218599
  • Title

    Persistent objects in the Fleet system

  • Author

    Malkhi, Dahlia ; Reiter, Michael K. ; Tulone, Daniela ; Ziskind, Elisha

  • Author_Institution
    Sch. of Comput. Sci. & Eng., Hebrew Univ., Jerusalem, Israel
  • Volume
    2
  • fYear
    2001
  • fDate
    2001
  • Firstpage
    126
  • Abstract
    Fleet is a middleware system implementing a distributed repository for persistent Java objects. Fleet is primarily targeted for supporting highly critical applications: in particular, the objects it stores maintain correct semantics despite the arbitrary failure (including hostile corruption) of a limited number of Fleet servers and, for some object types, of clients allowed to invoke methods on those objects. Fleet is designed to be highly available, dynamically extensible with new object types, and scalable to large numbers of servers and clients. In this paper, we describe the design of Fleet objects, including how new objects are introduced into the system, how they are named, and their default semantics
  • Keywords
    Java; client-server systems; distributed object management; persistent objects; system recovery; Fleet system; Java objects; availability; client failure; critical applications; default semantics; distributed repository; dynamically extensible system; hostile corruption; method invocation; middleware system; object design; object naming; object types; persistent objects; scalability; server failure; Buildings; Computer architecture; Computer science; Contracts; Fault tolerance; Java; Middleware; Protocols; Scalability; Software systems;
  • fLanguage
    English
  • Publisher
    ieee
  • Conference_Titel
    DARPA Information Survivability Conference & Exposition II, 2001. DISCEX '01. Proceedings
  • Conference_Location
    Anaheim, CA
  • Print_ISBN
    0-7695-1212-7
  • Type

    conf

  • DOI
    10.1109/DISCEX.2001.932165
  • Filename
    932165