X-Git-Url: http://git.indexdata.com/?a=blobdiff_plain;f=doc%2Fmulti.xml;h=13830f07a5375dc4049f3ab032075c217de0597f;hb=75eedebe94c90cf8b72499594fa7f5a12f34c192;hp=3d83e0ec149212f1e74ebfebd30d9484c4f7f103;hpb=9960226abe1700d3dc87e68529755e5cff09f0d9;p=metaproxy-moved-to-github.git diff --git a/doc/multi.xml b/doc/multi.xml index 3d83e0e..13830f0 100644 --- a/doc/multi.xml +++ b/doc/multi.xml @@ -1,36 +1,40 @@ - - - %common; + + %idcommon; ]> - - + + + Metaproxy + Index Data + + multi 3mp - Metaproxy Module - - + Metaproxy Module + + multi 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. + + + A target element is not required for multi-plexing to work. + It merely serves as a way to route differently. If an empty @@ -41,8 +45,40 @@ but simply ignored (unless every one of the databases is 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: + + z3950.loc.gov:7090/voyager + bagel.indexdata.dk/gils + * + +]]> + + + + + SEE ALSO @@ -57,21 +93,13 @@ - + ©right;