X-Git-Url: http://git.indexdata.com/?p=yazproxy-moved-to-github.git;a=blobdiff_plain;f=NEWS;h=7e4d466abd32492ee92c0e59dda007eb8a7fc956;hp=cc8c5cacef42d517b2f05ad63695891eeac7a56a;hb=6b3595eef97514b76b3c3b1e5c06b2fbba3bbbe4;hpb=f0845c46c919418d18c1a7881b10cb7cc691a42f

diff --git a/NEWS b/NEWS
index cc8c5ca..7e4d466 100644
--- a/NEWS
+++ b/NEWS
@@ -1,29 +1,101 @@
---- 1.2.0 2005/04/27
+--- 1.3.8 2012/11/29
+
+Allow backendelementset to be given for syntax section of configuration.
+
+Fix memory leak for SRU scan.
+ 
+--- 1.3.7 2012/09/05
+
+SRU scan support. By Rustam T. Usmanov.
+
+--- 1.3.6 2011/02/10
+
+Use libyaz4.
+
+Make yazproxy work with USEMARCON 3.15.
+
+--- 1.3.5 2009/12/03
+
+Prepare for 64-bit YAZ. yazproxy will still work with YAZ++ 1.1.4 or
+later which means YAZ 3.0.47 or later.
+
+--- 1.3.4 2008/06/06
+
+Omit debian directory from tar dist.
+
+--- 1.3.3.2 2008/05/27
+
+Match SRU database (PATH) against target name. Allow omitted explain
+section in configuration for SRU.
+
+--- 1.3.3.1 2008/05/21
+
+Z39.50 authentication user is no longer set to client-IP for SRU.
+
+--- 1.3.3 2008/03/20
+
+Added support for limiting the number of sockets (connections) to
+a particular backend. The new setting is called 'max-sockets' and
+must be defined in the target section.
+
+API verson 3 of USEMARCON is used. Patch by Ere Maijala.
+
+--- 1.3.2 2008/02/29
+
+Added option -D for yazproxy which puts yazproxy in background after
+startup.
+
+Fixed bug #2060: Killing yazproxy parent does not kill the child as well.
+
+--- 1.3.1 2007/12/27
+
+Fixed bug #1989: For PQF SRU one char is stipped off query.
+
+Fixed bug #1821: Wrong order of include directories for compiling.
+
+Allow EXSLT to be used if it's available.
+
+--- 1.3.0 2007/05/09
+
+Debian packages libyazproxy2, libyazproxy2-dev. These depend on
+libyazpp2, libyazpp2-dev.
+
+Branch out: YAZPROXY_1_2_1_1_branch .
+
+--- 1.2.1.1 2006/06/09
+
+Added support for thread config element which specifies number of
+threads to be used for auhentication modules. By default, no threading
+is used which happen to be value 0. Modules will still work but they will
+be blocking.
+
+--- 1.2.1 2006/05/01
+
+Fixed problem with log of session ID when HTTP fowarded was in effect.
 
 Fixed a problem with negative numbers in present requests.
 
-Allow client-ip to be logged for each log entry. Speciy
+Allow client-ip to be logged for each log entry. Specify
 <log>client-ip</log> in the configuration.
 
-Added support for limiting the number of initiating connections
-from a single IP. limit-connect specifies a limit and if that
-is reached a delay is introduced (just as limit-pdu, etc).
-Also added a new setting max-connect; if that max value is
-reached for a single IP the proxy will terminate the initiating
-session/connection immediately.
+Added support for limiting the number of initiating connections from
+a single IP. limit-connect specifies a limit and if that is reached a
+delay is introduced (just as limit-pdu, etc). Also added a new setting
+max-connect; if that max value is reached for a single IP the proxy
+will terminate the initiating session/connection immediately.
 
-New directive default-client-charset which serves as charset
-to be negotiated if client does NOT supports one.
+New directive default-client-charset which serves as charset to be
+negotiated if client does NOT supports one.
 
 Added support for threaded authentication modules. See
 etc/config-modules.xml + mod_sample.cpp for an example.
 
-Added support for Z39.50 character set negotiation. This allows
-the proxy to act as a Z39.50 server supporting character set negotiation
+Added support for Z39.50 character set negotiation. This allows the
+proxy to act as a Z39.50 server supporting character set negotiation
 for backends not supporting it. New config element target-charset
-specifies encoding for target, and MUST be specified in order
-for any conversion to take place. Conversion also takes place for
-SRW/SRU clients that are negotiate implicitly to UTF-8.
+specifies encoding for target, and MUST be specified in order for
+any conversion to take place. Conversion also takes place for SRW/SRU
+clients that are negotiate implicitly to UTF-8.
 
 --- 1.0.1 2005/05/27