Clix - A Hybrid Programming Environment for Distributed Objects and Distributed Shared Memory

Authors:
Frank Mueller;Jörg Nolte;Alexander Schlaefer
Affiliations:
-;-;-
Venue:
IPDPS '00 Proceedings of the 15 IPDPS 2000 Workshops on Parallel and Distributed Processing
Year:
2000

Citing 9
Cited 0

Memory coherence in shared virtual memory systems

ACM Transactions on Computer Systems (TOCS)
CC++: a declarative concurrent object-oriented programming notation

Research directions in concurrent object-oriented programming
An evaluation of software-based release consistent protocols

Journal of Parallel and Distributed Computing - Special issue on distributed shared memory systems
Design of the Munin distributed shared memory system

Journal of Parallel and Distributed Computing - Special issue on distributed shared memory systems
Scope consistency: a bridge between release consistency and entry consistency

Proceedings of the eighth annual ACM symposium on Parallel algorithms and architectures
ARTS of PEACE—a high-performance middleware layer for parallel distributed computing

Journal of Parallel and Distributed Computing - Special issue on software support for distributed computing
Easy-to-Use Object-Oriented Parallel Processing with Mentat

Computer
PANDA - Supporting Distributed Programming in C++

ECOOP '93 Proceedings of the 7th European Conference on Object-Oriented Programming
Distributed pC++ Basic Ideas for an Object Parallel Language

Scientific Programming

Quantified Score

Hi-index	0.00

Visualization

Abstract

Parallel programming with distributed object technology becomes increasingly popular but shared-memory programming is still a common way of utilizing parallel machines. In fact, both models can coexist fairly well and software DSM systems can be constructed easily using distributed object systems. In this paper, we describe the construction of a hybrid programming platform based on the Arts distributed object system. We describe how an object-oriented design approach provides a compact and flexible description of the system components. A sample implementation demonstrates that three classes of less than 100 lines of code each suffice to implement sequen tial consistency.