ScienceDirect® Home Skip Main Navigation Links
You have guest access to ScienceDirect. Find out more.
 
Home
Browse
My Settings
Alerts
Help
 Quick Search
 Search tips (Opens new window)
    Clear all fields    
advertisementadvertisement
Information and Software Technology
Volume 46, Issue 7, June 2004, Pages 445-455
 
Font Size: Decrease Font Size  Increase Font Size
 Abstract - selected
Article
Purchase PDF (167 K)

 
 
 
Related Articles in ScienceDirect
View More Related Articles
 
View Record in Scopus
 
doi:10.1016/j.infsof.2003.09.017    How to Cite or Link Using DOI (Opens New Window)
Copyright © 2003 Elsevier B.V. All rights reserved.

A distributed execution environment for shared java objects

Nadia Erdogan Corresponding Author Contact Information, E-mail The Corresponding Author, Yunus Emre Selcuk E-mail The Corresponding Author and Ozgur Sahingoz E-mail The Corresponding Author

Department of Computer Engineering, Electrical-Electronics Engineering Faculty, Istanbul Technical University, 80686 Ayazaga, Istanbul, Turkey

Received 4 March 2002; 
Revised 11 September 2003; 
accepted 11 September 2003. 
Available online 27 November 2003.

Purchase the full-text article



References and further reading may be available for this article. To view references and further reading you must purchase this article.

Abstract

This paper discusses the implementation of a distributed execution environment, DJO, which supports the use of shared Java objects for parallel and distributed applications and provides the Java programmer with the illusion of a network-wide shared object space on loosely coupled distributed systems. DJO supports shared objects through an implementation of multiple reader/single writer write-invalidate DSM protocol in software, providing the shared memory abstraction at object granularity. Object distribution and sharing are implemented through the replication mechanism, transparently to application. The system enforces mutual consistency among replicas of an object. The main benefits of DJO are enhanced availability and performance due to the replicated object model and easier application design, as the underlying software takes care of distribution and memory consistency issues.

Author Keywords: Author Keywords: Replication; Consistency management; Concurrency control; Distributed object system; Java

Article Outline

1. Introduction
2. Requirements and related work
3. Read-replication algorithm
3.1. Consistency maintenance
3.1.1. The consistency model: release consistency
3.1.2. The coherency protocol
4. Replicated object software architecture
4.1. Communication management module
4.2. The coherency protocol
4.2.1. Memory management component
4.2.2. Ownership management component
4.2.3. Distribution management component
4.3. Synchronization module
4.4. Consistency manager
5. User interface
5.1. Create a shared object
5.2. Remove a shared object
5.3. Access a shared object in read-only mode
5.4. Receive exclusive access to the shared object
5.5. To release exclusive access and save modified object state
6. Performance evaluation
7. Conclusion and future work
appendix a
References




 
Home
Browse
My Settings
Alerts
Help
Elsevier.com (Opens new window)
About ScienceDirect  |  Contact Us  |  Information for Advertisers  |  Terms & Conditions  |  Privacy Policy
Copyright © 2008 Elsevier B.V. All rights reserved. ScienceDirect® is a registered trademark of Elsevier B.V.