X-Git-Url: http://sru.miketaylor.org.uk/?a=blobdiff_plain;f=doc%2Fbook.xml;h=2d7c88d07971ba2fb71a3a6dfe1e8f63e4a49de3;hb=cf6a8ee04e21c58389a287ab5a7870fcc7453e6b;hp=fb39a879e88fa4718cbf1766f2ca418cd28006ee;hpb=03e2fc2fbd11931ca4183c3f1fb678f09eb5403e;p=metaproxy-moved-to-github.git

diff --git a/doc/book.xml b/doc/book.xml
index fb39a87..2d7c88d 100644
--- a/doc/book.xml
+++ b/doc/book.xml
@@ -18,7 +18,6 @@
      -->
      <!NOTATION PDF SYSTEM "PDF">
 ]>
-<!-- $Id: book.xml,v 1.63 2008-02-27 11:08:49 adam Exp $ -->
 <book id="metaproxy">
  <bookinfo>
   <title>Metaproxy - User's Guide and Reference</title>
@@ -158,10 +157,8 @@
      <listitem>
       <para>
        The popular C++ library. Initial versions of Metaproxy
-       was built with 1.33.0. Version 1.33.1 works too. Metaproxy
-       also compiles with Boost 1.34.1 but the tests do
-       <emphasis>not</emphasis> compile, because the Test API
-       of Boost has changed.
+       was built with 1.32 but this is no longer supported.
+       Metaproxy is known to work with Boost version 1.33 / 1.34 / 1.35.
       </para>
      </listitem>
     </varlistentry>
@@ -326,7 +323,7 @@
    <para>
     Metaproxy can be compiled with Microsoft
     <ulink url="&url.vstudio;">Visual Studio</ulink>.
-    Version 2003 (C 7.1) and 2005 (C 8.0) is known to work.
+    Versions 2003 (C 7.1), 2005 (C 8.0) and 2008 (C 9.0) is known to work.
    </para>
    <section id="installation.windows.boost">
     <title>Boost</title>
@@ -372,7 +369,7 @@
     <title>YAZ++</title>
     <para>
      Get <ulink url="&url.yazplusplus;">YAZ++</ulink> as well.
-     Version 1.0.3 or later is required.
+     Version 1.1.0 or later is required.
     </para>
     <para>
      YAZ++ includes NMAKE makefiles, similar to those found in the
@@ -1128,11 +1125,19 @@ Figure out what additional information we need in:
     &lt;metaproxy xmlns="http://indexdata.com/metaproxy" version="1.0"&gt;
    </screen>
    <para>
-    The top-level element is &lt;metaproxy&gt;.  This contains a
-    &lt;start&gt; element, a &lt;filters&gt; element and a
-    &lt;routes&gt; element, in that order.  &lt;filters&gt; is
-    optional; the other two are mandatory.  All three are
-    non-repeatable.
+    The top-level element is &lt;metaproxy&gt;.  This contains
+    a &lt;dlpath&gt; element,
+    a &lt;start&gt; element,
+    a &lt;filters&gt; element and
+    a &lt;routes&gt; element, in that order.  &lt;dlpath&gt; and
+    &lt;filters&gt; are optional; the other two are mandatory.
+    All four are non-repeatable.
+   </para>
+   <para>
+     The &lt;dlpath;&gt; element contains a text element which 
+     specifies the location of filter modules. This is only needed
+     if Metaproxy must load 3rd party filters (most filters with Metaproxy
+     are built into the Metaproxy application).
    </para>
   <para>
     The &lt;start&gt; element is empty, but carries a
@@ -1185,6 +1190,7 @@ Figure out what additional information we need in:
    </para>
    <screen><![CDATA[<?xml version="1.0"?>
 <metaproxy xmlns="http://indexdata.com/metaproxy" version="1.0">
+  <dlpath>/usr/lib/metaproxy/modules</dlpath>
   <start route="start"/>
   <filters>
     <filter id="frontend" type="frontend_net">