From: Sebastian Hammer Date: Wed, 11 Apr 2007 04:51:23 +0000 (+0000) Subject: Updated doc to describe settings command (settings can also be controlled from X-Git-Tag: PAZPAR2.1.0.0~331 X-Git-Url: http://git.indexdata.com/?a=commitdiff_plain;h=24ad2e0dd6ad8ac83c3b09831bcd3ecf9d601616;p=pazpar2-moved-to-github.git Updated doc to describe settings command (settings can also be controlled from the init command). --- diff --git a/doc/pazpar2_protocol.xml b/doc/pazpar2_protocol.xml index 5d25969..b976787 100644 --- a/doc/pazpar2_protocol.xml +++ b/doc/pazpar2_protocol.xml @@ -8,7 +8,7 @@ %common; ]> - + Pazpar2 @@ -59,7 +59,10 @@ ]]> - The + The init command may take a number of setting parameters, similar to + the 'settings' command described below. These settings are immediately + applied to the new session. + ping @@ -84,6 +87,46 @@ ]]> + + settings + + The settings command applies session-specific settings to one or more + databases. A typical function of this is to enable access to + restricted resources for registered users, or to set a user- or + library-specific username/password to use against a target. Each + setting parameter has the form name[target]=value, where name is the + name of the setting (e.g. pz:authentication), target is a target ID, + or possibly a wildcard, and value is the desired value for the + setting. + + + + Because the settings command manipulates potentially sensitive + information, it is possible to configure pazpar2 to only allow access + to this command from a trusted site -- usually from server-side + scripting, which in turn is responsible for authenticating the user, + and possibly determining which resources he has access to, etc. + + + + Note: As a shortcut, it is also possible to override settings directly in + the init command. + + + + Example: + + Response: + + OK + +]]> + + + search Launches a search, parameters: