Netscape DIRECTORY SERVER 6.01 - DEPLOYMENT Deployment Manual page 91

However, Server A does not contain the information requested. Instead, Server
4.
A returns a referral to the client application telling them to contact Server B.
The client application then sends a bind request to Server B. To bind
5.
successfully, Server B must also contain an entry for the client application.
The bind is successful, and the client application can now resubmit its search
6.
operation to Server B.
This approach requires Server B to have a replicated copy of the client's entry from
Server A.
Chaining solves this problem. A search request would occur as follows on a
chained system:
In the illustration above, the following steps are performed:
The client application binds with Server A and Server A tries to confirm that
1.
the user name and password are correct.
Server A does not contain an entry corresponding to the client application.
2.
Instead, it contains a database link to Server B, which contains the actual entry
of the client. Server A sends a bind request to Server B.
Server B sends an acceptance response to Server A.
3.
Server A then processes the client application's request using the database link.
4.
The database link contacts a remote data store located on Server B to process
the search operation.
About Knowledge References
Chapter 5 Designing the Directory Topology 91