| M. Dmitriev and M. Atkinson, Evolutionary Data Conversion in the PJama Persistent Language, In 1st ECOOP Workshop on Object-Oriented Databases, Lisbon, Portugal, 1999. |
....PJama offers orthogonal persistence by reachability. In practice, an application programmer wanting to store application data persistently adds just a few lines of code to her software, and all application data persist on disk for an unlimited length of time 9 . PJama has evolution facilities [8, 14] enabling new versions of software and data to replace the old ones, recovery support [13] which uses logging to guarantee system recovery on failure, and distribution support [24, 22] PJama stores offer good performance, and are ideally suited to fast application development, as they free the ....
M. Dmitriev and M. P. Atkinson. Evolutionary Data Conversion in the PJama Persistent Language. In Proceedings of the 1st ECOOP Workshop on Object-Oriented Databases, Lisbon, Portugal, June 1999.
No context found.
:2369#2376, 1999. #20# M. Dmitriev and M. P. Atkinson. Evolutionary Data Conversion in the PJama Persistent Language. In 1st ECOOP Workshop on ObjectOriented Databases, pages 25#36, Lisbon, Portugal,
....PJama offers orthogonal persistence by reachability. In practice, an application programmer wanting to store application data persistently adds just a few lines of code to her software, and all application data persists on disk for an unlimited length of time 5 . PJama has evolution facilities [14, 22, 5], enabling new versions of software and data to replace the old ones, recovery support [21] which uses logging to guarantee system recovery on failure, and distribution support [40, 38] PJama stores offer good performance, and are ideally suited to fast application development, as they free the ....
M. Dmitriev and M. P. Atkinson. Evolutionary Data Conversion in the PJama Persistent Language. In Proceedings of the 1st ECOOP Workshop on Object-Oriented Databases, Lisbon, Portugal, June 1999.
....mutated objects as this would have quickly jammed the disk buffer pool with mutated pages. 11 Minor releases tracked the successive versions of the JDK and added improvements to algorithms and orthogonality. Our next major step was the introduction of a stop the world eager evolution system [76, 78] ( 8) in PJama 0:2 released in August 1998. This version also included our first release of persistence support for Java RMI [196, 194] 11) By now, we were able to run a persistent version of the application that demonstrates the ( 12.1 ) Swing user interface components and a substantial GIS ....
....to the whole store. However, it is scalable, it carries out consistency checks, runs to completion or restores the store to its original state, and is completely general. The main steps in an evolution are described below and more fully in [96, 77] background and evaluation can be found in [76, 78, 17] (the last of these includes performance measurements) Specify the Set of Class Changes and Instance Transformations The developer generates, or obtains in the case of third party code, a set of revised classes and asks the evolution tool, opjb, to install them in a specified store. ....
M. Dmitriev and M.P. Atkinson. Evolutionary Data conversion in the PJama Persistent Language. In Proceedings of the First ECOOP Workshop on Object-Oriented Databases, 1999.
No context found.
M. Dmitriev and M. Atkinson, Evolutionary Data Conversion in the PJama Persistent Language, In 1st ECOOP Workshop on Object-Oriented Databases, Lisbon, Portugal, 1999.
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC