64 </blockquote>
  65 
  66 <h4>Names</h4>
  67 <p>
  68 Every naming method in the <tt>Context</tt>
  69 interface has two
  70 overloads: one that accepts a 
  71 <tt>Name</tt> argument and one that accepts a string name.
  72 <tt>Name</tt> is an interface that represents a generic 
  73 name--an ordered sequence of zero of more components.
  74 For these methods, <tt>Name</tt> can be used to represent a
  75 <em>composite name</em> (<tt>CompositeName</tt>)
  76 so that you can name an object using a name which spans multiple namespaces.
  77 <p>
  78 The overloads that accept <tt>Name</tt>
  79 are useful for applications that need to manipulate names: composing
  80 them, comparing components, and so on.
  81 The overloads that accept string names are likely to be more useful
  82 for simple applications, such as those that simply read in a name
  83 and look up the corresponding object.
  84 <p>
  85 
  86 <h4>Bindings</h4>
  87 
  88 The <tt>Binding</tt> class represents a name-to-object binding.
  89 It is a tuple containing the name of the bound object,
  90 the name of the object's class, and the object itself.
  91 <p>
  92 The <tt>Binding</tt> class is actually a subclass of
  93 <tt>NameClassPair</tt>, which consists
  94 simply of the object's name and the object's class name.
  95 The <tt>NameClassPair</tt> is useful when you only want
  96 information about the object's class and do not want to
  97 pay the extra cost of getting the object.
  98 
  99 <h4>References</h4>
 100 Objects are stored in naming and directory services in different ways.
 101 If an object store supports storing Java objects, 
 102 it might support storing an object in its serialized form.
 103 However, some naming and directory services do not support the
 104 storing of Java objects. Furthermore, for some

  64 </blockquote>
  65 
  66 <h4>Names</h4>
  67 <p>
  68 Every naming method in the <tt>Context</tt>
  69 interface has two
  70 overloads: one that accepts a 
  71 <tt>Name</tt> argument and one that accepts a string name.
  72 <tt>Name</tt> is an interface that represents a generic 
  73 name--an ordered sequence of zero of more components.
  74 For these methods, <tt>Name</tt> can be used to represent a
  75 <em>composite name</em> (<tt>CompositeName</tt>)
  76 so that you can name an object using a name which spans multiple namespaces.
  77 <p>
  78 The overloads that accept <tt>Name</tt>
  79 are useful for applications that need to manipulate names: composing
  80 them, comparing components, and so on.
  81 The overloads that accept string names are likely to be more useful
  82 for simple applications, such as those that simply read in a name
  83 and look up the corresponding object.

  84 
  85 <h4>Bindings</h4>
  86 
  87 The <tt>Binding</tt> class represents a name-to-object binding.
  88 It is a tuple containing the name of the bound object,
  89 the name of the object's class, and the object itself.
  90 <p>
  91 The <tt>Binding</tt> class is actually a subclass of
  92 <tt>NameClassPair</tt>, which consists
  93 simply of the object's name and the object's class name.
  94 The <tt>NameClassPair</tt> is useful when you only want
  95 information about the object's class and do not want to
  96 pay the extra cost of getting the object.
  97 
  98 <h4>References</h4>
  99 Objects are stored in naming and directory services in different ways.
 100 If an object store supports storing Java objects, 
 101 it might support storing an object in its serialized form.
 102 However, some naming and directory services do not support the
 103 storing of Java objects. Furthermore, for some