mirror of
https://git.openldap.org/openldap/openldap.git
synced 2025-12-24 08:39:37 -05:00
(ITS#5718) [documentation] Mention dontusecopy control in conjunctionwith slapo-chain(5)
This commit is contained in:
parent
721264db13
commit
f6a49e6b66
1 changed files with 14 additions and 0 deletions
|
|
@ -322,6 +322,20 @@ side, the actual error is returned to the client.
|
|||
> chain-return-error TRUE
|
||||
|
||||
|
||||
H3: Read-Back of Chained Modifications
|
||||
|
||||
Occasionally, applications want to read back the data that they just wrote.
|
||||
If a modification requested to a shadow server was silently chained to its
|
||||
producer, an immediate read could result in receiving data not yet sync'ed.
|
||||
In those cases, clients should use the {{B:dontusecopy}} control to ensure
|
||||
they are directed to the authoritative source for that piece of data.
|
||||
|
||||
This control usually causes a referral to the actual source of the data
|
||||
to be returned. However, when the {{slapo-chain(5)}} overlay is used,
|
||||
it intercepts the referral being returned in response to the
|
||||
{{B:dontusecopy}} control, and tries to fetch the requested data.
|
||||
|
||||
|
||||
H3: Further Information
|
||||
|
||||
{{:slapo-chain(5)}}
|
||||
|
|
|
|||
Loading…
Reference in a new issue