X-Git-Url: http://git.indexdata.com/?p=yaz-moved-to-github.git;a=blobdiff_plain;f=doc%2Fgfs-virtual.xml;h=18d68ddc4dca163a3b6bc38c81d74a5e9dc4c2f5;hp=340b641d6f966c0d3b95bb9546a345814d7f1369;hb=48b7a077523d1a86c16c9f536c56d6439fe90f42;hpb=162d5174d5fa510c0ee6810ae6bc0ee5f7c6fd61

diff --git a/doc/gfs-virtual.xml b/doc/gfs-virtual.xml
index 340b641..18d68dd 100644
--- a/doc/gfs-virtual.xml
+++ b/doc/gfs-virtual.xml
@@ -1,5 +1,4 @@
-<!-- 
-   $Id: gfs-virtual.xml,v 1.3 2005-08-05 09:36:15 adam Exp $
+<!--
    Description of the virtual host mechanism in YAZ GFS
    Included in both manual and man page for yaz-ztest
 -->
@@ -30,7 +29,7 @@
 </note>
 <para>
  The YAZ frontend server uses XML to describe the backend
- configurations. Command-line option <literal>-f</literal> 
+ configurations. Command-line option <literal>-f</literal>
  specifies filename of the XML configuration.
 </para>
 <para>
@@ -40,14 +39,14 @@
 </para>
 <para>
  The <literal>listen</literal> describes listener (transport end point),
- such as TCP/IP, Unix file socket or SSL server. Content for 
+ such as TCP/IP, Unix file socket or SSL server. Content for
  a listener:
  <variablelist>
   <varlistentry><term>CDATA (required)</term>
    <listitem>
     <para>
      The CDATA for the <literal>listen</literal> element holds the
-     listener string, such as <literal>tcp:@:210</literal>, 
+     listener string, such as <literal>tcp:@:210</literal>,
      <literal>tcp:server1:2100</literal>,
      etc.
     </para>
@@ -130,11 +129,45 @@
     <para>
      Specifies a filename that includes CQL to RPN conversion for this
      backend server. See &reference-tools-cql-map;
-     If given, the backend server will only "see" a Type-1/RPN query. 
+     If given, the backend server will only "see" a Type-1/RPN query.
     </para>
    </listitem>
   </varlistentry>
-   
+
+  <varlistentry><term>element <literal>ccl2rpn</literal> (optional)</term>
+   <listitem>
+    <para>
+     Specifies a filename that includes CCL to RPN conversion for this
+     backend server. See &reference-tools-ccl-qualifiers;
+     If given, the backend server will only "see" a Type-1/RPN query.
+    </para>
+   </listitem>
+  </varlistentry>
+
+  <varlistentry><term>element <literal>stylesheet</literal> (optional)</term>
+   <listitem>
+    <para>
+     Specifies the stylesheet reference to be part of SRU HTTP responses
+     when the client does not specify one. If neither this is given, nor
+     the client specifies one, no stylesheet reference is part of the
+     SRU HTTP response.
+    </para>
+   </listitem>
+  </varlistentry>
+
+  <varlistentry><term>element <literal>docpath</literal> (optional)</term>
+   <listitem>
+    <para>
+     Specifies a path for local file access using HTTP. All URLs with
+     a leading prefix (/ exluded) that matches the value of docpath
+     are used for file access. For example, if the server is to offer
+     access in directory <literal>xsl</literal>, the docpath would be
+     <literal>xsl</literal> and all URLs of the form
+     <literal>http://host/exl</literal> will result in a local file access.
+    </para>
+   </listitem>
+  </varlistentry>
+
   <varlistentry><term>element <literal>explain</literal> (optional)</term>
    <listitem>
     <para>
@@ -145,9 +178,32 @@
     </para>
    </listitem>
   </varlistentry>
+
+  <varlistentry><term>element <literal>maximumrecordsize</literal> (optional)</term>
+   <listitem>
+    <para>
+     Specifies maximum record size/message size, in bytes. This
+     value also servers as maximum size of <emphasis>incoming</emphasis>
+     packages (for Record Updates etc). It's the same value as that
+     given by the <literal>-k</literal> option.
+    </para>
+   </listitem>
+  </varlistentry>
+
+  <varlistentry><term>element <literal>retrievalinfo</literal> (optional)</term>
+   <listitem>
+    <para>
+     Enables the retrieval facility supporting conversions and
+     specifications of record formats/types.
+     See <xref linkend="tools.retrieval"/> for
+     more information.
+    </para>
+   </listitem>
+  </varlistentry>
+
  </variablelist>
 </para>
- 
+
 <para>
  The XML below configures a server that accepts connections from
  two ports, TCP/IP port 9900 and a local UNIX file socket.