From: Adam Dickmeiss <adam@indexdata.dk>
Date: Thu, 20 Oct 2005 07:16:47 +0000 (+0000)
Subject: Imagined config for yp2.
X-Git-Tag: YP2.0.0.2~195
X-Git-Url: http://git.indexdata.com/?a=commitdiff_plain;h=1eca35ef242c6cb9f8ce1f9bd00b494579ce1915;p=metaproxy-moved-to-github.git

Imagined config for yp2.
---

diff --git a/etc/config1.xml b/etc/config1.xml
new file mode 100644
index 0000000..d5629a5
--- /dev/null
+++ b/etc/config1.xml
@@ -0,0 +1,31 @@
+<?xml version="1.0"?>
+<!-- imagined config for yp2..
+  The router system understands yp2, sequence and filter elements.
+  Everything else interpreted by filters.
+  Each filter is invoked in a sequence (unless a filter invokes another
+  sequence.. A start sequence must be determined somehow.
+  -->
+<yp2>
+  <sequence name="start">
+    <filter type="frontend-net"> <!-- the Z39.50/HTTP frontend -->
+      <port>210</port>
+    </filter>
+    <filter type="log">          <!-- apply logging always -->
+      <logfile>mylog.log</logfile>
+    </filter>
+    <filter type="cond">           <!-- conditional -->
+      <invoke sequence="public">   <!-- invoke public sequence for some db -->
+            port=210 and db="public" 
+      </invoke>
+    </filter>
+    <filter name="reject">        <!-- reject .. -->
+    </filter>
+  </sequence>
+  <sequence name="public">
+    <filter type="z3950-client">
+      <target>localhost:9999/A</target>
+    </filter>
+  </sequence>
+</yp2>
+
+<!-- observation: the logic could be controlled by a XSLT! -->