From 1700f4d992fbbc7ec607ed1daa1228cdb7dc251f Mon Sep 17 00:00:00 2001 From: Mike Taylor Date: Tue, 16 May 2006 10:32:54 +0000 Subject: [PATCH] Describe --- doc/book.xml | 23 ++++++++++++++++++++++- doc/multi.xml | 11 ++++++++++- 2 files changed, 32 insertions(+), 2 deletions(-) diff --git a/doc/book.xml b/doc/book.xml index b3ab960..384e1a7 100644 --- a/doc/book.xml +++ b/doc/book.xml @@ -1,4 +1,4 @@ - + Metaproxy - User's Guide and Reference @@ -1184,6 +1184,27 @@ Z> be metasearched in this way: issues of resource usage and administrative complexity dictate the practical limits. + + What happens when one of the databases doesn't respond? By default, + the entire multi-database search fails, and the appropriate + diagnostic is returned to the client. This is usually appropriate + during development, when technicians need maximum information, but + can be inconvenient in deployment, when users typically don't want + to be bothered with problems of this kind and prefer just to get + the records from the databases that are available. To obtain this + latter behaviour add an empty + <hideunavailable> + element inside the + <multi>: + + + + ]]> + + Under this regime, an error is reported to the client only if + all the databases in a multi-database search + are unavailable. + diff --git a/doc/multi.xml b/doc/multi.xml index 54afb63..201844e 100644 --- a/doc/multi.xml +++ b/doc/multi.xml @@ -2,7 +2,7 @@ "http://www.oasis-open.org/docbook/xml/4.1/docbookx.dtd" [ ]> - + multi @@ -30,6 +30,15 @@ ]]> + + If an empty + <hideunavailable> + element is placed inside the + multi + filter, then unavailable databases are not reported to the client, + but simply ignored (unless every one of the databases is + unanavailable). + SEE ALSO -- 1.7.10.4