This paper describes proposed extensions to the Ada95 programming language to provide support for persistent programming. The extensions support transparent migration of data between a program's address space and a persistent store in a way that preserves both type safety and encapsulation of ADT's. 1 Introduction Ada has recently undergone an intensive and major review and update. The result of this is the new programming language Ada95 (ISO 1995) which is, in the main, backward compatible with Ada83. Two of the principle changes to Ada was the addition of appropriate semantic constructs to change Ada from an objectbased language to a fully fledged object-oriented language and the provision of annexes defining additional language capabilities for specific user communities. In this paper we consider further extensions to Ada95 by way of the introduction of a persistence annex to provide persistent programming support to Ada. We call this revision persistent Ada95 to distinguish it fr...

. Research into persistent programming languages and systems in recent years has shown that the technology is useful for developing complex software in many problem domains. This paper explores the issues and consequences of adding persistence to Ada95. The persistence extensions support transparent migration of objects between a program's address space and a persistent store in a way that preserves both type safety and encapsulation of abstract data types. Keywords and Phrases: Kinds of systems: persistent systems; Ada95; object-oriented technology. 1 Introduction Ada has recently undergone an intensive and major review and update. The result of this is the new programming language Ada95[23] which is, in the main, backward compatible with Ada83[36]. Two of the principle changes to Ada were the addition of new constructs to change it from an object-based language to a fully fledged object-oriented language and the provision of annexes defining additional language capabilities for spec...

Our native Java compiler directly generates runtime structures in a persistent Distributed Shared Memory (DSM). The compiler has been used to build a general purpose PC Operating System (OS) on top of a persistent DSM memory. The persistent DSM operating environment lends itself naturally to an integration of symbol tables, class descriptors and naming during Java program compilation and execution.

Abstract: Transactions and recoverable memories are powerful mechanisms for handling failures and manipulating persistent data. Unfortunately, standard recoverable memories incur an overhead of several milliseconds per transaction. This paper presents a system that improves transaction overhead by a factor of 2000 for working sets that fit in main memory. Of this factor of 2000, a factor of 20 is due to the Rio file cache, which absorbs synchronous writes to disk without losing data during system crashes. The remaining factor of 100 is due to Vista, a 720-line, recoverable-memory library tailored for Rio. Vista lowers transaction overhead to 5 μsec by using no redo log, no system calls, and only one memory-to-memory copy. This drastic reduction in overhead leads to a overall speedup of 150-556x for benchmarks based on TPC-B and TPC-C. 1.

The purpose of the work describe here is to gain experimental experience with data warehouses for large collections of Java objects. We report on the design, architecture, and early experimental work with a software tool called JTool for creating data warehouses of Java objects. Our primary interest is in building distributed data warehouses containing large collections of Java objects as a basis for the data mining of objects on the web. This work is broadly based upon our prior work with a software called PTool which we have used for the data mining of large collections of C++ objects in clustered computing environments [Grossman 1996 and 1997a]. 1 This research was supported by Grants from the National Science Foundation and the Department of Energy. 2 Robert Grossman is a also a member of the technical staff at Magnify, Inc. With Version 0.2 of JTool, we have built Gigabyte size data warehouses of Java objects and showed that JTool scales linearly with the size of the warehous...

Abstract not found