Persistence in the Spring system

5Citations
Citations of this article
11Readers
Mendeley users who have this article in their library.
Get full text

Abstract

The Spring system does not provide persistent object identifiers and not all Spring objects are persistent. Instead, we rely on a general name service and persistent name-to-object bindings to support persistence. The name service is separate from the various subsystems that implement persistent objects, so that new object types can be added, and the implementation of existing types can be changed, without rebuilding the name service. We distinguish among the concepts of freezing, pickling, and externalizing. We then develop a general framework for freezing that can be used by any client, including the name server,for making objects persistent. It allows subsystems that implement objects of various types to maintain autonomy from the name service and retain control over how their objects are implemented and made persistent, and yet be well integrated with the name service.

Cite

CITATION STYLE

APA

Radia, S., Madany, P., & Powell, M. L. (1993). Persistence in the Spring system. In Proceedings - 3rd International Workshop on Object Orientation in Operating Systems, IWOOOS 1993 (pp. 12–23). Institute of Electrical and Electronics Engineers Inc. https://doi.org/10.1109/IWOOOS.1993.324931

Register to see more suggestions

Mendeley helps you to discover research relevant for your work.

Already have an account?

Save time finding and organizing research with Mendeley

Sign up for free