From f6a49e6b6669584d16ac97da9f6f7cd7fbeab54f Mon Sep 17 00:00:00 2001 From: Gavin Henry Date: Tue, 30 Sep 2008 11:51:35 +0000 Subject: [PATCH] (ITS#5718) [documentation] Mention dontusecopy control in conjunctionwith slapo-chain(5) --- doc/guide/admin/overlays.sdf | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/doc/guide/admin/overlays.sdf b/doc/guide/admin/overlays.sdf index 48dd94d02a..8987caa462 100644 --- a/doc/guide/admin/overlays.sdf +++ b/doc/guide/admin/overlays.sdf @@ -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)}} -- 2.39.5