+Setting XML files are now stored in etc/settings instead of etc. This
+reflects the layout with the Debian package layout.
+
+Settings may be posted for command=settings. The POSTed settings must
+have root element 'settings' like regular setting files. In order to be
+recognized, the POST request must use Content-Type=text/xml.
+
+A service may be posted for command=init. This service will be used
+during the session. The service may have its own target settings,
+ICU config, timeout, etc. In order to be recognized, the POST request
+must use Content-Type=text/xml.
+
+Timeout values may be given per-service. That's element 'timeout'
+which takes three attribute values (a subset may be given): 'session',
+'z3950_operation', 'z3950_session'. Option -T is no longer supported
+- used to specify session timeout.
+
+Option -t tests the Pazpar2 configuration and returns exit code
+(0=success, non-zero=failure). In previous version of Pazpar2, -t
+specified local settings.
+
+In version 1.2.0 the configuration file - after include processing -
+was dumped to stdout. Now, the configuration is only dumped to the
+yaz log file if option -d is given.
+
+--- 1.2.0 2009/09/10
+
+Configuration may now have multiple server areas. This means that a
+Pazpar2 instance may listen on multiple ports. Virtual hosting is not
+yet supported - on a server basis. Configuration may also have multiple
+services .. That is repeating service elements inside a server. Each
+has an attribute 'id' which serves as service ID. This ID in turn may
+be used in a Pazpar2 session, by specifying parameter service=ID for
+command init. There can be at most one unnamed service inside a server
+which can be referred to by not specifying an service ID for command
+init (backwards compatible). In order to partition multiple servers and
+services a new include directive has been added. This takes an attribute
+'src' which specifies one or more sub-files. For example to include
+service files, one might use:
+ <server >.. <include src=/"etc/pazpar2/conf.d/*.xml"/> .. </server>.
+It is the intention that that completely makes the settings directive
+redundant.
+
+Fix problem where the record command would wait forever if there were
+no targets to wait for (activeclients == 0).
+
+--- 1.1.1 2009/08/28
+
+One result set is created per session (last search) rather than for
+each connection which happen to be shared (bug #3009).
+
+marc21 stylesheets changed for efficiency.
+
+--- 1.1.0 2009/08/19
+
+Session timeout may be specified on the command-line as option -T.
+
+Pazpar2 may now be operated in a no-merged mode for records.. All records
+will be considered unique. This mode is enabled if no mergekey is
+generated by the normalization stylesheet (pz:xslt).
+
+Pazpar2 caches original records from each target and the 'record' command
+with offset returns the original record if 'syntax' and 'esn' are NOT
+specified. This speeds up retrieval of original records but also means
+that Pazpar2 uses more memory. The cached records will be freed when the
+session terminates or a new search is executed.
+
projects / pazpar2-moved-to-github.git / blobdiff