C. Lamb, G. Landis, J. Orenstein, and D. Weinreb, The ObjectStore Database system, Communications of the ACM 34(10), 1991, pp. 51-63. Home/Search Document Not in Database Summary ACM TOC Related Articles Check |
This paper is cited in the following contexts:
First 50 documents Next 50
Safe Class and Data Evolution in Large and Long-Lived Java.. - Dmitriev (2001) (10 citations) (Correct)
....development environments. Instead of traditional, and apparently inappropriate, approach of using files, directories or ad hoc persistence schemes, it was proposed to use some kind of persistent object technology [JV95] The initial prototype was developed, written in C and using ObjectStore [LLOW91] for the persistent facilities. In 1995 the growing popularity of Java became obvious, so the Forest team refocused their efforts on it and decided to re implement their system in Java. However, no persistence mechanism was available at that time that was free of the pitfalls encountered when ....
C. Lamb, G. Landis, J. Orestein, and D. Weinreb. The ObjectStore database system. Communications of the ACM, 34(10):50--63, October 1991.
Fault Resilience In Main-Memory Databases: Handling Process.. - Bohannon (1999) (Correct)
.... 52] Other memory mapped databases are designed to support high performance fault tolerant applications [28] for example the Dali Main Memory Storage Manager [13] Research into object oriented database systems, such as EXODUS [14, 15] and Ode [2] as well as the success of commercial products [46, 67], has served to demonstrate that a memory mapped architecture with direct application access to data is critical for a significant class of applications. Other memory resident or memory mapped storage architectures such as Recoverable Virtual Memory [65] Cricket [66] and Texas Store [70] have ....
.... but such communication is orders of magnitude slower than access in the same process space, even with highly tuned implementations [8] Due to this cost, an increasing number of systems give application code direct access to system buffers, including extensible systems [73] object databases [46, 3], and memory mapped or in memory architectures [41, 66, 70] In [75] Sullivan and Stonebraker investigate the use of hardware memory protection to improve software fault tolerance in a DBMS environment by guarding data in the buffer cache. For example, calls were added to POSTGRES [73] to ....
[Article contains additional citation context not shown here]
C. Lamb, G. Landis, J. Orenstein, and D. Weinreb. The ObjectStore database system. CACM, 34(10):51--63, October 1991.
Software Circulation using Sandboxed File Space -.. - Kato, Oyama, Kanda.. (Correct)
....computer site. This combination of unloading and loading corresponds to the go operation provided by other mobile object agent systems. The design and implementation of the mobile memory segment is a#ected by persistent memory segments provided by persistent object systems, such as ObjectStore [11], and single level store operating systems such as Multics [2] and Opal [5] Most modern operating systems support the allocation and mapping of multiple memory segments to files in a file system. This technique 2 is called a memory mapped file. Furthermore, recent operating systems support ....
C. Lamb, G. Landis, J. Orenstein, and D. Weinreb. The ObjectStore database system. Comm. of the ACM, 34(10):50--63, Oct. 1991.
The Distributed Interoperable Object Model and Its Application.. - Liu, al. (1995) (13 citations) (Correct)
....access to the individual data repositories. The DION linking database should be considered just as yet another persistent data repository in the DION architecture. In the first phase, we intend to implement the link database using an object oriented database management system such as ObjectStore [7]. We now explain in more detail the basic concepts of DION and its mechanisms to further address questions like: How does DION enable cross database interoperability What makes DION such a useful and unifying model How does DION enhance the adaptiveness and robustness of the interoperable ....
J. C.Lamb, G.Landis and D. Weinreb. The objectstore database system. Commumcatiozs of the ACM, 34(10), 1991.
Grasshopper: An orthogonally persistent operating system - Dearle, di Bona, Farrow, .. (1994) (44 citations) (Correct)
....[4] This technique requires considerable complexity to ensure that objects are not loaded more than once and that objects are copied back to persistent storage atomically. Recently a large number of object oriented database implementations have appeared both commercially and as research vehicles [21, 33]. A large number of these have been based on the language C and rely upon the implementor changing the C run time system in some manner to load and store persistent data. One popular technique used by these systems is to overload the deference operator to perform residency checking [6] ....
Lamb, C., Landis, G., Orenstein, J. and Weinreb, D. "The Objectstore Database System", CACM, vol 34, 10, pp. 50-63, 1991.
The Distributed Interoperable Object Model and Its Application to .. - Liu, Pu (1995) (13 citations) (Correct)
....access to the individual data repositories. The DION linking database should be considered just as yet another persistent data repository in the DION architecture. In the first phase, we intend to implement the link database using an object oriented database management system such as ObjectStore [15]. Note that in Diorarea, there is neither a single global database containing the integrated information nor even a global database schema that describes all the information accessible via Diorarea. Each application may set up its own interoperable interface schema using DIaN IDL. One of the key ....
C. Lamb, G. Landis, J. Orenstein, and D. Weinreb. The objectstore database system. Commuicatios of the ACM, 34(10), 1991.
JPS: A Distributed Persistent Java System - Boyapati (1998) (3 citations) (Correct)
....complex long lived data. These systems are drawing increasing interest from application designers whose data requirements are not met by traditional data management systems. Commonly cited application areas that use persistent object stores include computer aided software engineering (CASE) tools [LLOW91] computer aided design and computer aided manufacturing (CAD CAM) CDN93] geographical information systems (GIS) DKL 94] oce automation and document preparation systems [BM92] Since Java [GJS96] has no persistence model built into it, the tremendous growth in the popularity of Java has ....
C. Lamb, G. Landis, J. Orenstein, and D. Weinreb. The ObjectStore database system. In Communications of the ACM 34(10), October 1991.
TDB: A Database System for Digital Rights Management - Vingralek, Maheshwari, Shapiro (2001) (1 citation) (Correct)
....mind. In PS algol and Thor, transient and persistent objects are defined and used similarly; persistence is determined by reachability from a persistent root, and unreachable objects are garbage collected. ObjectStore provides persistence for regular C classes without furnishing its own compiler [19]. It does use a tool to parse C class representations and virtual memory techniques to manage persistence. These techniques are not suitable for embedded environments that do not provide virtual memory. Some object oriented database systems, such as GemStone [24] provide automatic index ....
C. Lamb, G. Landis, J. Orenstein, and D. Weinreb. The ObjectStore database system. Communications of the ACM, 34, 1991.
Execution Performance Issues in Full-Text Information Retrieval - Brown (1995) (9 citations) (Correct)
....particularly low overhead along the critical path of object access. Memory resident objects are quickly located using the resident object table, and non resident objects are faulted in with little additional processing. This can be contrasted with page mapping architectures of other object stores [49, 77] which have a fairly high penalty for accessing a non resident object. These systems are optimized for localized processing of a large number of small objects, where the cost of faulting a page of objects can be amortized over many access to the objects in the page. This pattern of access differs ....
Lamb, C., Landis, G., Orenstein, J., and Weinreb, D. The ObjectStore database system. Commun. ACM, 34(10):50--63, Oct. 1991.
Object Storage Management Architectures - Biliris, Orenstein (1994) (3 citations) Self-citation (Orenstein) (Correct)
No context found.
C. Lamb, G. Landis, J. Orenstein, and D. Weinreb. The ObjectStore database system. Communications of the ACM, 34#10#:51#63, October 1991.
Path Constraints in Semistructured Databases - Peter Buneman Department (1 citation) (Correct)
No context found.
C. Lamb, G. Landis, J. Orenstein, and D. Weinreb, The ObjectStore Database system, Communications of the ACM 34(10), 1991, pp. 51-63.
Improving the I/O Performance and Correctness of Network File.. - Wang (1999) (Correct)
No context found.
Lamb, C., Landis, G., Orenstein, J., and Weinreb, D. (1991). The ObjectStore Database System. Communications of the ACM, 34(10):50--63. 181
Virtual Log Based File Systems for a Programmable Disk - Wang, Anderson, Patterson (1999) (30 citations) (Correct)
No context found.
Lamb, C., Landis, G., Orenstein, J., and Weinreb, D. The ObjectStore Database System. Communications of the ACM 34, 10 (October 1991), 50--63.
A Survey of Object Oriented Databases - Demeyer (1992) (Correct)
No context found.
Lamb, C. / Landis, G. / Orenstein, J. / Weinreb, D. "The Objectstore database system" Communications of the ACM, Vol. 34(10), Oct. 91
Persistence in Distributed Object Systems: ORB/ODBMS Integration - Reverbel (1996) (1 citation) (Correct)
No context found.
Lamb, C., G. Landis, J. Orenstein, and D. Weinreb, "The ObjectStore Database System", Communications of the ACM , Vol. 34, No. 10, pp. 50--63, October 1991. Also in [54].
LOTS: A Software DSM Supporting Large Object Space - Cheung, Wang, Lau (2004) (Correct)
No context found.
C. Lamb, G. Landis, J. Orenstein, D. Weinreb, "The ObjectStore Database System", Communications of the ACM, Vol. 34, No. 10, October 1991.
Khazana: A Flexible Wide Area Data Store - Sai Susarla And (2003) (Correct)
No context found.
C. Lamb, G. Landis, J. Orenstein, and D. Weinreb. The Objectstore database system. Communications of the ACM, Oct. 1991.
Composable Consistency for Large-scale - Peer Replication Sai (2003) (Correct)
No context found.
C. Lamb, G. Landis, J. Orenstein, and D. Weinreb. The Objectstore database system. CACM, Oct. 1991.
Two-Stage Transaction Processing in Client-Server DBMSs - Vinay Kanitkar And (Correct)
No context found.
C. Lamb, G. Landis, J. Orenstein, and D. Weinreb. The ObjectStore Database System. Communications of the ACM, 34(10), October 1991.
Views Or Points Of View On Images - Oria, Al. (2003) (Correct)
No context found.
C. Lamb, G. Landis, J. Orenstein, and D. Weinreb, "The objectstore database system, " Commun. ACM 34(10), 19--20 (1991).
An Adaptive Data-Shipping Architecture for Client Caching .. - Voruganti, Özsu, Unrau (2003) (Correct)
No context found.
Lamb, C., G. Landis, J. Orenstein, and D. Weinreb: 1991, `The ObjectStore database system'. Communications of the ACM 34(10), 50--63.
GeoWeb: a Multiframe Web Interface to ObjectStore-based - Spatial Data Repositories (2001) (Correct)
No context found.
C. Lamb, G. Landis, J. Orenstein, and D. Weinreb. The ObjectStore database system. Communications of the ACM, 34(10):50--63, 1991.
Software---Practice And Experience, Vol. 25(10).. - Migration In.. (Correct)
No context found.
C. Lamb, G. Landis, J. Orenstein and D. Weinreb, `The ObjectStore database system', Communications of the ACM, 34, (10), 50--63 (1991).
Making C++ Objects Persistent: the Hidden Pointers - Biliris, Dar, Gehani (1993) (1 citation) (Correct)
No context found.
C. Lamb, G. Landis, J. Orenstein and D. Weinreb, `The ObjectStore database system', Comm. ACM, 34, (10), 50--63 (1991).
Fine-granularity Locking and Client-Based Logging.. - Panagos, Biliris.. (1996) (3 citations) (Correct)
No context found.
C. Lamb, G. Landis, J. Orenstein, and D. Weinreb. The ObjectStore database system. Communications of the ACM, 34#10#:51#63, October 1991.
First 50 documents Next 50
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC