X-Git-Url: http://lists.indexdata.com/cgi-bin?a=blobdiff_plain;f=doc%2Fbook.xml;h=384e1a7ec0a9c5ec043a6224991752ca9d7634dd;hb=1700f4d992fbbc7ec607ed1daa1228cdb7dc251f;hp=b3ab960b0a2c5da2ccbe0ad7464afdc472e4bb61;hpb=29ba846c074cdcedb1cf4e52efdbd0b9822d5ba6;p=metaproxy-moved-to-github.git

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 @@
-<!-- $Id: book.xml,v 1.30 2006-05-03 14:56:07 mike Exp $ -->
+<!-- $Id: book.xml,v 1.31 2006-05-16 10:32:54 mike Exp $ -->
  <bookinfo>
   <title>Metaproxy - User's Guide and Reference</title>
   <author>
@@ -1184,6 +1184,27 @@ Z>
     be metasearched in this way: issues of resource usage and
     administrative complexity dictate the practical limits.
    </para>
+   <para>
+    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
+    <literal>&lt;hideunavailable&gt;</literal>
+    element inside the
+    <literal>&lt;multi&gt;</literal>:
+   </para>
+   <screen><![CDATA[      <filter type="multi">
+        <hideunavailable/>
+      </filter>]]></screen>
+   <para>
+    Under this regime, an error is reported to the client only if
+    <emphasis>all</emphasis> the databases in a multi-database search
+    are unavailable.
+   </para>
   </section>