Migration in CORBA component model

Authors:
Jacek Cała
Affiliations:
AGH-University of Science and Technology, Department of Computer Science
Venue:
DAIS'07 Proceedings of the 7th IFIP WG 6.1 international conference on Distributed applications and interoperable systems
Year:
2007

Citing 9
Cited 0

Amoeba: A Distributed Operating System for the 1990s

Computer
COOL: kernel support for object-oriented environments

OOPSLA/ECOOP '90 Proceedings of the European conference on object-oriented programming on Object-oriented programming systems, languages, and applications
Transparent process migration in the Sprite operating system

Transparent process migration in the Sprite operating system
The RHODOS migration facility

Journal of Systems and Software
Understanding Code Mobility

IEEE Transactions on Software Engineering
Binding, migration, and scalability in CORBA

Communications of the ACM
Process migration

ACM Computing Surveys (CSUR)
Portable serialization of CORBA objects: a reflective approach

OOPSLA '02 Proceedings of the 17th ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications
Live migration of virtual machines

NSDI'05 Proceedings of the 2nd conference on Symposium on Networked Systems Design & Implementation - Volume 2

Quantified Score

Hi-index	0.01

Visualization

Abstract

Migration of running application code is considered a very attractive and desired mechanism to improve application performance, resource sharing, self-adaptability, etc. This mechanism seems to be even more important nowadays, considering the growing interest in the area of mobile computing and mobile networks. This paper briefly presents a migration mechanism for a CORBA Component Model platform. We discuss general issues related to migration of running code, further elaborated in the context of CCM. We also propose an extension to the original CCM model which provides interfaces to implement migration. The paper presents the most important problems which appeared during implementation of a prototype facility and it discusses possible solutions. One of the most fundamental issues related to mobility of running code is the residual dependency problem. The intention of the work is not to provide a solution to this (possibly unsolvable) problem, but to propose an approach which would make programmers aware of its existence. Thus, the paper allows readers to make more conscious decisions when designing their components. The paper ends with an evaluation of the prototype implementation on top of Open CCM, an open source Java implementation of the CORBA Component Model.