X-Git-Url: http://sru.miketaylor.org.uk/?a=blobdiff_plain;f=doc%2Fload_balance.xml;h=f71a29433a7cebb8d55fddf314a64f46cef38bff;hb=31977dc8d6996d2de009d62739ee5f688ba77504;hp=5fdf57e6aaf4429439a50c70bd718128fd7767a9;hpb=601933683c68801e86c4f1380b70a8972eaa1cb1;p=metaproxy-moved-to-github.git

diff --git a/doc/load_balance.xml b/doc/load_balance.xml
index 5fdf57e..f71a294 100644
--- a/doc/load_balance.xml
+++ b/doc/load_balance.xml
@@ -4,7 +4,6 @@
  <!ENTITY % idcommon SYSTEM "common/common.ent">
      %idcommon;
 ]>
-<!-- $Id: load_balance.xml,v 1.4 2007-05-22 11:05:45 adam Exp $ -->
 <refentry id="ref-load_balance">
  <refmeta>
   <refentrytitle>load_balance</refentrytitle>
@@ -23,23 +22,35 @@
    This filter balances load among Z39.50 targets based on statistics
    gathered on number of open sessions and number of open package requests. 
   </para>
+  <para>
+   The load balancing is depending on targets to be specified (vhosts).
+   Most Z39.50 clients do not specify that. For this reason, this
+   filter is mostly used as a follower to filter virt_db.
+  </para>
  </refsect1>
  
  <refsect1><title>EXAMPLES</title>
   <para>
-   A typical configuration looks like this:
+   This configuration offers one database, <literal>Default</literal>,
+   which is load-balanced between two backend servers.
    <screen><![CDATA[
+    <filter type="virt_db"/>
+      <database>Default</database>
+      <target>host1:210/Default</target>
+      <target>host2:210/Default</target>
+    </filter>
     <filter type="load_balance"/>
 ]]>
    </screen>
   </para>
+  
  </refsect1> 
  
  <refsect1><title>SEE ALSO</title>
   <para>
    <citerefentry>
-    <refentrytitle>metaproxy</refentrytitle>
-    <manvolnum>1</manvolnum>
+    <refentrytitle>virt_db</refentrytitle>
+    <manvolnum>3mp</manvolnum>
    </citerefentry>
   </para>
  </refsect1>