X-Git-Url: http://git.indexdata.com/?p=yaz-moved-to-github.git;a=blobdiff_plain;f=doc%2Fzoom.xml;h=00592b784f4f16ce76294918b28dac1f97785d99;hp=a9d97aef6a5bf8f7640889b31a0eaf109f039cd4;hb=ccb068efa655ace7835a122c1226356f2f933992;hpb=0718fd63660899964512631d1e246ded8e3d18d6

diff --git a/doc/zoom.xml b/doc/zoom.xml
index a9d97ae..00592b7 100644
--- a/doc/zoom.xml
+++ b/doc/zoom.xml
@@ -1,4 +1,4 @@
-<!-- $Id: zoom.xml,v 1.22 2003-02-21 00:24:26 adam Exp $ -->
+<!-- $Id: zoom.xml,v 1.27 2003-05-20 08:22:33 adam Exp $ -->
  <chapter id="zoom"><title>ZOOM</title>
   <para>
     &zoom; is an acronym for 'Z39.50 Object-Orientation Model' and is
@@ -11,8 +11,8 @@
   <note>
    <para>
     A recent addition to &yaz; is SRW support. You can now make
-    SRW ZOOM connections by specifying a new scheme for the
-    host name for a connection.
+    SRW ZOOM connections by specifying scheme <literal>http://</literal>
+    for the hostname for a connection.
    </para>
   </note>
 
@@ -167,6 +167,11 @@
         targetImplementationVersion</entry><entry> Implementation Version
         of target.
        </entry><entry>none</entry></row>
+      <row><entry>
+        databaseName</entry><entry>One or more database names
+        separated by character plus (<literal>+</literal>), which to
+        be used by subsequent search requests on this Connection.
+       </entry><entry>Default</entry></row>
      </tbody>
     </tgroup>
    </table>
@@ -233,16 +238,18 @@
     </sect2>
    <sect2><title>SRW Protocol behavior</title>
     <para>
-     The SRW protocol doesn't feature an Init Request, so
+     The SRW protocol doesn't feature an Inititialize Request, so
      the connection phase merely establishes a TCP/IP connection
      with the SOAP service.
     </para>
-    <para>None of the ZOOM connection options
+    <para>Most of the ZOOM connection options do not
      affect SRW and they are ignored. However, future versions
      of &yaz; might honor <literal>implementationName</literal> and
      put that as part of User-Agent header for HTTP requests.
-     The <literal>charset</literal>, and <literal>lang</literal>
-     might also affect HTTP headers in future releases.
+     </para>
+    <para>
+     The <literal>charset</literal> is used in the Content-Type header
+     of HTTP requests.
     </para>
    </sect2>
   </sect1>
@@ -353,6 +360,10 @@
         count</entry><entry>Number of records to be retrieved.
        </entry><entry>0</entry></row>
       <row><entry>
+        step</entry><entry>Number of records to be retrieved in
+        one chunk. The value, 0 means unchunked.
+       </entry><entry>0</entry></row>
+      <row><entry>
         elementSetName</entry><entry>Element-Set name of records. 
         Most targets should honor element set name <literal>B</literal>
         and <literal>F</literal> for brief and full respectively.
@@ -388,10 +399,6 @@
         The element set name to be for medium-sized result sets.
        </entry><entry>none</entry></row>
       <row><entry>
-        databaseName</entry><entry>One or more database names
-        separated by character plus (<literal>+</literal>).
-       </entry><entry>Default</entry></row>
-      <row><entry>
         setname</entry><entry>Name of Result Set (Result Set ID).
         If this option isn't set, the ZOOM module will automatically
         allocate a result set name.