Name
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. |
Year | DOI | Venue |
|---|---|---|
1996 | 10.1145/236337.236351 | OOPSLA |
Field | DocType | Volume |
Programming language,Software engineering,Reuse,Computer science,Common Object Request Broker Architecture,Real-time computing,Externalization | Conference | 31 |
Issue | ISSN | ISBN |
10 | 0362-1340 | 0-89791-788-X |
Citations | PageRank | References |
8 | 1.36 | 20 |
Authors | ||
3 | ||
Name | Order | Citations | PageRank |
|---|---|---|---|
| Jan Kleindienst | 1 | 220 | 23.74 |
| Frantisek Plasil | 2 | 945 | 74.69 |
| Petr Tuma | 3 | 276 | 31.77 |