Naming policies in the Spring system

Abstract

The Spring name service does not prescribe particular naming policies; instead it serves as a foundation for building various policies. Our default policy is an environment containing name spaces for naming system-supplied objects, for a user's objects, for objects shared across applications, and for objects private to a process. Some name spaces are private, while others are shared. Any name space can be configured by attaching arbitrary name spaces from different parts of the distributed environment. We also use ordered merge constructions for further flexibility in tailoring name spaces. Each executing process is given a private name space to which other name spaces, such as the user's name space, system-supplied name spaces, and other shared name spaces are attached. Our scheme gives great flexibility in sharing objects and name spaces in a distributed computing environment. Name spaces can be configured dynamically to take advantage of local resources during distributed execution.<>