Why FNS?

FNS is useful for the following reasons:

• A single uniform naming interface is provided to clients for accessing different naming services. As a consequence, the addition of new naming services does not require changes to applications or to existing member naming services. Furthermore, application developers need to learn and use only one naming interface.

• Names can be composed in a uniform way, and the resulting composite names can have any number of components. This allows the composite namespace to serve the needs of many diversed applications.

• Coherent naming is encouraged through the use of shared contexts and shared names. This reduces duplication of effort in individual applications when supplying similar functionality.