Complex Directory Lookup using Java Based LDAP Query Extension
draft-goenka-ldapext-java-complex-search-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Vishal Goenka | ||
| Last updated | 1999-06-02 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
LDAP provides some simple primitives to construct search filters. Complex LDAP search queries such as those involving joins or functional evaluation of simple query results require client side processing of the intermediate search results. The network overhead of retrieving intermediate results can be substantial for large databases. This document defines an LDAP extension for supporting server side evaluation of complex search queries. Custom search logic can be sent across to the server, encapsulated as a Java Object. The LDAP server supporting this extension would instantiate the java object and invoke its well known interfaces in a JVM. The java object running at the server end acts as the client-proxy, and makes a local search query to the LDAP server. The directory entries are evaluated using the custom logic embedded in the client-proxy, and those that satisfy the evaluation function are returned as the search result to the LDAP server, which passes it back to the originating client. Even non-Java LDAP clients can use this method, provided the search query is written as a java object.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)