Refactor URI utils to uri.c

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

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

  <chapter id="introduction"><title>Introduction</title>
 
   <para>
  <chapter id="introduction"><title>Introduction</title>
 
   <para>

@@ -32,6 +31,7 @@
      </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).
       <ulink url="&url.openssl;">OpenSSL</ulink>.
       If enabled, &yaz; uses HTTPS transport (for SOAP) or
       "Secure BER" (for Z39.50).

@@ -97,7 +97,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 +160,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.