<chapter id="proxy">
- <!-- $Id: proxy.xml,v 1.2 2002-10-21 13:37:31 adam Exp $ -->
+ <!-- $Id: proxy.xml,v 1.4 2002-10-22 14:04:17 mike Exp $ -->
<title>YAZ Proxy</title>
<para>
The YAZ proxy is a transparent Z39.50 to Z39.50 gateway.
It is useful for debugging Z39.50 software, redirect
- Z39.50 packages through firewalls, etc.
+ Z39.50 packages through fire walls, etc.
</para>
<para>
Furthermore, the proxy offers facilities that often
It does not store "state" information on the hard drive
except the log files you want.
</para>
- <section><title>Specifying the backend target</title>
+ <section id="proxy-target">
+ <title>Specifying the backend target</title>
<para>
When a Z39.50 client session is accepted by the proxy, the proxy
determines the backend target by the following rules:
<orderedlist>
<listitem>
<para> If the Initialize Request PDU from the client
- includes OtherInformation, with OID,
+ includes Other-Information, with OID,
<literal>1.2.840.10003.10.1000.81.1</literal>, that
specifies the target.
</para>
</orderedlist>
</para>
</section>
- <section><title>Keep-alive facility for Stateless clients</title>
+ <section id="proxy-keepalive">
+ <title>Keep-alive facility for Stateless clients</title>
<para>
Stateless clients may generate a cookie for a Z39.50
session which is sent to the proxy as part of PDUs.
point of view should be considered stateless.
</para>
<para>
- As for the target specification, the OtherInformation
+ As for the target specification, the Other-Information
area is used to hold the cookie with OID
<literal>1.2.840.10003.10.1000.81.2</literal>.
</para>
</section>
- <section><title>Query Caching</title>
+ <section id="proxy-cache">
+ <title>Query Caching</title>
<para>
Simple stateless clients often sends identical Z39.50 searches
in a relatively short period of time (full-list, next-page,
</section>
- <section><title>Other optimizations</title>
+ <section id="proxy-optimizations">
+ <title>Other optimizations</title>
<para>
We've had some plans to support caching of result set records,
but this had not yet been implemented.
</para>
</section>
- <section><title>Proxy usage</title>
+
+ <section id="proxy-usage">
+ <title>Proxy usage</title>
<para>
</para>
<refentry id="yaz-proxy">
<refsect1><title>DESCRIPTION</title>
<para>
- The proxy is a daemon on its own and runs standalone (no
+ The proxy is a daemon on its own and runs stand-alone (no
inetd support). The host:port specifies host address and
listening port respectively. Use <literal>@</literal>
for ANY address.
<listitem><para>
Sets level for optimization. Use zero to disable; non-zero
to enable. Handling for this is not fully implemented;
- we will probably use a bitmask to enable/disable specific
+ we will probably use a bit mask to enable/disable specific
features.
</para></listitem>
</varlistentry>