Lessons learned from implementing the CORBA persistent object service

  • Authors:

  • Jan Kleindienst;František Plášil;Petr Tůma

  • Affiliations:

  • Institute of Computer Science, Czech Academy of Sciences, Pod vodárenskou vĕží, 180 00 Prague 8, Czech Republic;Charles University, Faculty of Mathematics and Physics, Department of Software Engineering, Malostranské námestí 25, 118 00 Prague 1, Czech Republic and Institute of Computer Scienc ...;Charles University, Faculty of Mathematics and Physics, Department of Software Engineering, Malostranské námestí 25, 118 00 Prague 1, Czech Republic

  • Venue:
  • Proceedings of the 11th ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications
  • Year:
  • 1996

Quantified Score

Hi-index 0.00

Visualization

Abstract

In this paper, the authors share their experiences gathered during the design and implementation of the CORBA Persistent Object Service. There are two problems related to a design and implementation of the Persistence Service: first, OMG intentionally leaves the functionality core of the Persistence Service unspecified; second, OMG encourages reuse of other Object Services without being specific enough in this respect. The paper identifies the key design issues implied both by the intentional lack of OMG specification and the limits of the implementation environment characteristics. At the same time, the paper discusses the benefits and drawbacks of reusing other Object Services, particularly the Relationship and Externalization Services, to support the Persistence Service. Surprisingly, the key lesson learned is that a direct reuse of these Object Services is impossible.