X-Git-Url: http://git.indexdata.com/?a=blobdiff_plain;f=doc%2Fmulti.xml;h=e4281d932ad7a9a6575d77bc211ec3c98c477ef4;hb=4e5fbe510b39e6697927a98a5b6f0877929f999e;hp=db80beb13de041a7e5c376789c5959b4026ccf62;hpb=a7d0816d8e587b0743cdfda1cbb2321315be7946;p=metaproxy-moved-to-github.git diff --git a/doc/multi.xml b/doc/multi.xml index db80beb..e4281d9 100644 --- a/doc/multi.xml +++ b/doc/multi.xml @@ -1,37 +1,87 @@ - + + %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. 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 + <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 - A typical configuration looks as likes: + A typical configuration looks like this: + lx2.loc.gov:210/LCDB_MARC8 + z3950.indexdata.com/gils + localhost:9999 + * ]]> - - + + + SEE ALSO @@ -46,21 +96,13 @@ - + ©right;