X-Git-Url: http://jsfdemo.indexdata.com/?a=blobdiff_plain;ds=inline;f=doc%2Fmulti.xml;h=23e40a6f7f57f2c2bd7dfe828da4e86f878e52e5;hb=8be1f8ebc6a5578daeec06543feda12d5fb374d6;hp=201844efaaab91718f9d6fad279b31aeae5844b9;hpb=1700f4d992fbbc7ec607ed1daa1228cdb7dc251f;p=metaproxy-moved-to-github.git diff --git a/doc/multi.xml b/doc/multi.xml index 201844e..23e40a6 100644 --- a/doc/multi.xml +++ b/doc/multi.xml @@ -1,24 +1,67 @@ - + + %idcommon; ]> - - + + + Metaproxy + Index Data + + multi 3mp - Metaproxy Module - + Metaproxy Module + multi - package multiplexer + Metaproxy Package Multiplexer Module DESCRIPTION This filter multiplexes packages. + + 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 + <hideunavailable> + element is placed inside the + multi + filter, then unavailable databases are not reported to the client, + 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 @@ -26,19 +69,14 @@ A typical configuration looks like this: + z3950.loc.gov:7090/voyager + bagel.indexdata.dk/gils + * ]]> - - If an empty - <hideunavailable> - element is placed inside the - multi - filter, then unavailable databases are not reported to the client, - but simply ignored (unless every one of the databases is - unanavailable). - + SEE ALSO @@ -61,15 +99,7 @@