65 a naming context. 
  66 For example, the directory object for a person might contain
  67 the attributes of that person, and at the same time provide
  68 a context for naming objects relative to that person
  69 such as his printers and home directory.
  70 
  71 <h4>Searches</h4>
  72 <code>DirContext</code> contains methods for
  73 performing content-based searching of the directory.
  74 In the simplest and most common form of usage, the application
  75 specifies a set of attributes--possibly with specific
  76 values--to match, and submits this attribute set, to the
  77 <code>search()</code> method.
  78 There are other overloaded forms of <code>search()</code>
  79 that support more sophisticated <em>search filters</em>.
  80 
  81 
  82 <h2>Package Specification</h2>
  83 
  84 The JNDI API Specification and related documents can be found in the
  85 <a href="../../../../technotes/guides/jndi/index.html">JNDI documentation</a>.
  86 
  87 @since 1.3
  88 
  89 </body>
  90 </html>

  65 a naming context. 
  66 For example, the directory object for a person might contain
  67 the attributes of that person, and at the same time provide
  68 a context for naming objects relative to that person
  69 such as his printers and home directory.
  70 
  71 <h4>Searches</h4>
  72 <code>DirContext</code> contains methods for
  73 performing content-based searching of the directory.
  74 In the simplest and most common form of usage, the application
  75 specifies a set of attributes--possibly with specific
  76 values--to match, and submits this attribute set, to the
  77 <code>search()</code> method.
  78 There are other overloaded forms of <code>search()</code>
  79 that support more sophisticated <em>search filters</em>.
  80 
  81 
  82 <h2>Package Specification</h2>
  83 
  84 The JNDI API Specification and related documents can be found in the
  85 {@extLink jndi_overview JNDI documentation}.
  86 
  87 @since 1.3
  88 
  89 </body>
  90 </html>