-<!-- $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>
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><hideunavailable></literal>
+ element inside the
+ <literal><multi></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>
"http://www.oasis-open.org/docbook/xml/4.1/docbookx.dtd" [
<!ENTITY copyright SYSTEM "copyright.xml">
]>
-<!-- $Id: multi.xml,v 1.4 2006-04-25 12:48:52 marc Exp $ -->
+<!-- $Id: multi.xml,v 1.5 2006-05-16 10:36:51 mike Exp $ -->
<refentry>
<refmeta>
<refentrytitle>multi</refentrytitle>
]]>
</screen>
</para>
+ <para>
+ If an empty
+ <literal><hideunavailable></literal>
+ element is placed inside the
+ <literal>multi</literal>
+ filter, then unavailable databases are not reported to the client,
+ but simply ignored (unless every one of the databases is
+ unanavailable).
+ </para>
</refsect1>
<refsect1><title>SEE ALSO</title>