X-Git-Url: http://lists.indexdata.com/cgi-bin?a=blobdiff_plain;f=etc%2Fpazpar2.cfg;h=3ccbda5ce84031d5d2898891190cda42fc778b99;hb=5c0b5b368867a9b8fe6c3ffe7887890584ee9643;hp=e63a98ca553611bffec6164d98d4b7d264e3eeda;hpb=dde4a5914bbb5511a91e73d8ab45210b48637596;p=pazpar2-moved-to-github.git

diff --git a/etc/pazpar2.cfg b/etc/pazpar2.cfg
index e63a98c..3ccbda5 100644
--- a/etc/pazpar2.cfg
+++ b/etc/pazpar2.cfg
@@ -5,13 +5,6 @@
      configuration.
 -->
 
-<!-- thought... right now there is only one global 'service' in the code, but
-     it will be pretty simple to make this repeatable, and I think that should
-     be done at some point (this will eliminate most of the global parameters.
-     But it might be nice to have 'virtual' targets, so differrent sets of
-     configuration could live within one listener (on a single
-     port). -->
-
 <server>
   <listen port="9004"/>
   <proxy host="localhost" port="80"/>
@@ -23,14 +16,8 @@
 
 <!-- Need to figure out where to get ZeeRex records for targets from -->
 
-<!-- The 'profiles' below are repeatable, and tagged with an ID, so that they
-     can be linked with targets. -->
-
-<!-- They can be generated dynamically using XSLT. -->
-
-<queryprofile/>  <!-- Like a CCL profile? What else? -->
-
-<!-- Select by target ID (pattern). What else???   -->
+<queryprofile/>  <!-- Like a CCL profile++ . Can optionally refer to XSLT to 
+       convert ZeeRex into queryprofile. Multiple profiles can exist.  -->
 
 <retrievalprofile>
   <requestsyntax>marc21</requestsyntax>