diff options
| author | Nalin Dahyabhai <nalin.dahyabhai@pobox.com> | 2008-04-29 19:43:22 -0400 |
|---|---|---|
| committer | Nalin Dahyabhai <nalin.dahyabhai@pobox.com> | 2008-04-29 19:43:22 -0400 |
| commit | 04db20825eeeb042e5688bcdf1ebc17925f40fd9 (patch) | |
| tree | 58bf72a7a940fb01bff54936fb6f2cdfa8e962e9 | |
| parent | 59e9543f29da1d55fe8eda1c4e69b4bd10e6f7c7 (diff) | |
- fix some wording
| -rw-r--r-- | doc/design.txt | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/doc/design.txt b/doc/design.txt index 78341eb..6a06412 100644 --- a/doc/design.txt +++ b/doc/design.txt @@ -130,9 +130,9 @@ data in the way that a NIS server might. protocol-handler side is the ability to find a given key and/or the successor key for a given key, and their matching data items. The backend requires that the cache also be able to track one or more DNs - which are relevant to the value which is being stored in the map, so - that it can be updated if an entry with that name is added, removed, - modified, or renamed.] + which are relevant to the value which is being stored for a given key + in the map, so that it can be updated if a directory entry with that DN + is added, removed, modified, or renamed.] Forcing queries to use the cache provides a couple of benefits over an alternate approach of performing an LDAP query for each NIS query: @@ -191,8 +191,8 @@ specifier given as the "valueFormat"]. To ensure safety, any reference to an attribute value which does not also specify an alternate value will cause the directory server entry to be ignored if the referenced attribute has no value defined for that - entry, or contains more multiple values. In the above example, the - entry would be ignored if the "uid", "uidNumber", "gidNumber", or + entry, or contains multiple values. In the above example, the entry + would be ignored if the "uid", "uidNumber", "gidNumber", or "homeDirectory" attributes of the entry did not each contain exactly one value. |