X-Git-Url: http://lists.indexdata.com/cgi-bin?a=blobdiff_plain;f=doc%2Fmulti.xml;h=4db632530e6ffec10452ae5ca21eab619a402e5a;hb=HEAD;hp=201844efaaab91718f9d6fad279b31aeae5844b9;hpb=1700f4d992fbbc7ec607ed1daa1228cdb7dc251f;p=metaproxy-moved-to-github.git diff --git a/doc/multi.xml b/doc/multi.xml index 201844e..4db6325 100644 --- a/doc/multi.xml +++ b/doc/multi.xml @@ -1,34 +1,42 @@ - + + %idcommon; ]> - - + + + Metaproxy + Index Data + + multi 3mp - Metaproxy Module - - + Metaproxy Module + + multi - package multiplexer + Metaproxy Package Multiplexer Module - + DESCRIPTION This filter multiplexes packages. - - - EXAMPLES - A typical configuration looks like this: - - -]]> - + The multi filter consists of zero or more + <target> elements. + If a target matches a given target specified as CDATA in the + target element, the multi filter will route traffic to the route + given by the route attribute. The target element may also apply + credentials to be sent to the target. This is given by the + auth attribute. + + + A target element is not required for multi-plexing to work. + It merely serves as a way to route differently. If an empty @@ -37,10 +45,43 @@ multi filter, then unavailable databases are not reported to the client, but simply ignored (unless every one of the databases is - unanavailable). + unavailable). + + + If an empty + <hideerrors> + element is placed inside the + multi + filter, then databases that reports diagnostics are not reported back + to the client, but simply ignored (unless every one of the databases report + diagnostics). - - + + + SCHEMA + + + + + EXAMPLES + + A typical configuration looks like this: + + lx2.loc.gov:210/LCDB_MARC8 + z3950.indexdata.com/gils + localhost:9999 + * + +]]> + + + + + SEE ALSO @@ -55,21 +96,13 @@ - + ©right;