Document the very useful ZOOM-C option "apdulog".

[yaz-moved-to-github.git] / doc / introduction.xml

diff --git a/doc/introduction.xml b/doc/introduction.xml
index d1a8bc5..fc9a628 100644 (file)
--- a/doc/introduction.xml
+++ b/doc/introduction.xml
@@ -1,9 +1,8 @@
-<!-- $Id: introduction.xml,v 1.25 2006-10-05 08:26:58 adam Exp $ -->

  <chapter id="introduction"><title>Introduction</title>
 
   <para>
    &yaz; is a C/C++ library for information retrieval applications
  <chapter id="introduction"><title>Introduction</title>
 
   <para>
    &yaz; is a C/C++ library for information retrieval applications

-   using the Z39.50/SRU protocols for information retrieval.
+   using the Z39.50/SRU/SOLR protocols for information retrieval.

   </para>
   
   <para>
   </para>
   
   <para>

@@ -17,7 +16,7 @@
     <listitem><para>
       Supports 
       <ulink url="&url.sru;">SRU GET/POST/SOAP</ulink>
     <listitem><para>
       Supports 
       <ulink url="&url.sru;">SRU GET/POST/SOAP</ulink>

-      version 1.1 (over HTTP and HTTPS).
+      version 1.2 (over HTTP and HTTPS).

      </para></listitem>
     <listitem><para>
       Includes BER encoders/decoders for the 
      </para></listitem>
     <listitem><para>
       Includes BER encoders/decoders for the 

@@ -25,6 +24,10 @@
       protocol.
      </para></listitem>
     <listitem><para>
       protocol.
      </para></listitem>
     <listitem><para>

+      Supports 
+      <ulink url="&url.solr;">SOLR</ulink> Web Service version 1.4.x (client side only)
+     </para></listitem>
+    <listitem><para>

       Supports the following transports: BER over TCP/IP
       (<ulink url="&url.ber.over.tcpip;">RFC1729</ulink>),
       BER over unix local socket, and 
       Supports the following transports: BER over TCP/IP
       (<ulink url="&url.ber.over.tcpip;">RFC1729</ulink>),
       BER over unix local socket, and 

@@ -32,14 +35,15 @@
      </para></listitem>
     <listitem><para>
       Secure Socket Layer support using
      </para></listitem>
     <listitem><para>
       Secure Socket Layer support using

+      <ulink url="&url.gnutls;">GNU TLS</ulink> or

       <ulink url="&url.openssl;">OpenSSL</ulink>.
       If enabled, &yaz; uses HTTPS transport (for SOAP) or
       "Secure BER" (for Z39.50).
      </para></listitem>
     <listitem><para>
       Offers 
       <ulink url="&url.openssl;">OpenSSL</ulink>.
       If enabled, &yaz; uses HTTPS transport (for SOAP) or
       "Secure BER" (for Z39.50).
      </para></listitem>
     <listitem><para>
       Offers 

-      <ulink url="&url.zoom;">ZOOM</ulink> C API implementing both
-      Z39.50 and SRU.
+      <ulink url="&url.zoom;">ZOOM</ulink> C API implementing
+      Z39.50, SRU and SOLR Web Service.

      </para></listitem>
     <listitem><para>
       The &yaz; library offers a set of useful utilities
      </para></listitem>
     <listitem><para>
       The &yaz; library offers a set of useful utilities

@@ -97,7 +101,7 @@
 
     <listitem>
      <para>
 
     <listitem>
      <para>

-      <xref linkend="client"/> describes how to use the &yaz; Z39.50
+      <xref linkend="yaz-client"/> describes how to use the &yaz; Z39.50

       client. If you're developer and wish to test your server
       or a server from another party, you might find this chapter
       useful.
       client. If you're developer and wish to test your server
       or a server from another party, you might find this chapter
       useful.

@@ -160,7 +164,7 @@
     toolkit offers several different levels of access to the
     <ulink url="&url.z39.50;">ISO23950/Z39.50</ulink>,
     <ulink url="&url.ill;">ILL</ulink> and
     toolkit offers several different levels of access to the
     <ulink url="&url.z39.50;">ISO23950/Z39.50</ulink>,
     <ulink url="&url.ill;">ILL</ulink> and

-    <ulink url="&url.sru;">SRU</ulink>/<ulink url="&url.srw;">SRW</ulink>
+    <ulink url="&url.sru;">SRU</ulink>

     protocols.
     The level that you need to use depends on your requirements, and
     the role (server or client) that you want to implement.
     protocols.
     The level that you need to use depends on your requirements, and
     the role (server or client) that you want to implement.