[interchange-docs] xmldocs - docelic modified 20 files

docs at icdevgroup.org docs at icdevgroup.org
Fri Jan 9 19:35:50 UTC 2009


User:      docelic
Date:      2009-01-09 19:35:50 GMT
Modified:  glossary gate
Modified:  guides   howtos.xml
Modified:  refs     IPCsocket ImageAlias ImageDir ImageDirSecure
Modified:           Inet_Mode ItemAction Jobs Levies Levy Limit Locale
Modified:           LocaleDatabase LogFile Mall MasterHost
Modified:           MaxQuantityField MimeType MoreDB
Log:
* Updates to I/J/K/L/M config directives

Revision  Changes    Path
1.2                  xmldocs/glossary/gate


rev 1.2, prev_rev 1.1
Index: gate
===================================================================
RCS file: /var/cvs/xmldocs/glossary/gate,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- gate	3 Aug 2006 21:58:40 -0000	1.1
+++ gate	9 Jan 2009 19:35:50 -0000	1.2
@@ -1,3 +1,11 @@
 In ⁣ parlance, "gating" is the process of controlling access to
-certain pages. See &howto-control-access-to-certain-pages; HOW-TO entry
+certain pages. See <olink targetdoc='howtos' targetptr='gate'/> HOW-TO entry
 for further information and examples.
+</para>
+	<note><para>
+		In &IC; versions prior to 5.7.0, <filename>.access</filename> file found
+		directly in &conf-PageDir; (i.e.
+		<filename class='directory'>pages/</filename>) is mistakenly ignored,
+		but does work for subdirectories.
+	</para></note>
+<para>



1.7                  xmldocs/guides/howtos.xml


rev 1.7, prev_rev 1.6
Index: howtos.xml
===================================================================
RCS file: /var/cvs/xmldocs/guides/howtos.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- howtos.xml	6 Jan 2009 13:22:45 -0000	1.6
+++ howtos.xml	9 Jan 2009 19:35:50 -0000	1.7
@@ -51,7 +51,7 @@
 <qandadiv><title>Interchange</title>
 
 	<qandadiv><title>Core</title>
-		<qandaentry><question><para>
+		<qandaentry><question id='gate'><para>
 		Controlling access to pages
 		</para></question><answer><para>
 There's a built-in &IC; way to control access to pages served
@@ -89,7 +89,11 @@
 </programlisting>
 <replaceable>PAGE_NAME</replaceable> is the name of page to be controlled,
 and the page suffix (such as <literal>.html</literal>) is optional.
-Page name of <literal>*</literal> can be used to set a default permission.
+</para><para>
+Page name of "<literal>*</literal>" can be used to set a default permission, but
+globbing is not possible ("<literal>ind*</literal>" will not match
+"<literal>index</literal>"). The default permission has lower precedence
+than any rule that matches the page name explicitly.
 </para><para>
 The <replaceable>CONDITION</replaceable> is a simple &glos-true; (or 
 <literal>Yes</literal>) or &glos-false; (or <literal>No</literal>) value
@@ -122,10 +126,6 @@
 *:        [data session logged_in]
 </programlisting>
 
-<!-- XXX is it first match wins, and can you say page*: ... ? 
-
--->
-
 		</para></answer></qandaentry>
 
 



1.3                  xmldocs/refs/IPCsocket


rev 1.3, prev_rev 1.2
Index: IPCsocket
===================================================================
RCS file: /var/cvs/xmldocs/refs/IPCsocket,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- IPCsocket	15 Feb 2008 18:24:50 -0000	1.2
+++ IPCsocket	9 Jan 2009 19:35:50 -0000	1.3
@@ -13,8 +13,8 @@
 
 
 __NAME__ description
-The directive specifies the filename which &IC; should create to enable
-IPC socket communication. The filename must, of course, be writable
+The directive specifies the filename IC; should create to enable
+IPC socket communication. The filename must be writable
 by the Interchange daemon.
 __END__
 



1.3                  xmldocs/refs/ImageAlias


rev 1.3, prev_rev 1.2
Index: ImageAlias
===================================================================
RCS file: /var/cvs/xmldocs/refs/ImageAlias,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- ImageAlias	6 Nov 2006 18:41:20 -0000	1.2
+++ ImageAlias	9 Jan 2009 19:35:50 -0000	1.3
@@ -19,7 +19,9 @@
 set by &conf-ImageDir; and related directives.
 </para><para>
 It is similar in effect to the "alias" feature of Web servers such as 
-&APACHE; or NCSA. 
+&APACHE; or NCSA, and applies to <literal>&lt;body background=</literal>, 
+table elements <literal>background=</literal> and all 
+<literal>src=</literal> specifications.
 __END__
 
 __NAME_ notes



1.5                  xmldocs/refs/ImageDir


rev 1.5, prev_rev 1.4
Index: ImageDir
===================================================================
RCS file: /var/cvs/xmldocs/refs/ImageDir,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- ImageDir	6 Nov 2006 18:41:20 -0000	1.4
+++ ImageDir	9 Jan 2009 19:35:50 -0000	1.5
@@ -17,31 +17,15 @@
 &conf-ImageDir; is one of quite basic settings in every &ccf;.
 </para><para>
 The directive specifies a base location, accessible over the web,
-where &IC; should look for IMG and INPUT &glos-HTML;
-<literal>src=</literal> file specifications.
-To be precise, actually, this setting applies to image locations mentioned
+where &IC; should look for image files, when just relative image
+filename is given.
+Automatically "translated" are image locations mentioned
 in <![CDATA[
 <img src="">, <input src="">, <body background="">, <table background=""> and table subelements (<th>, <tr> and <td>).]]>
 </para><para>
-As you might know, &IC; keeps its pages in a special directory
-<filename class='directory'>pages/</filename> (which is a subdirectory of 
-your catalog's &glos-CATROOT;). That directory can be readable only by the 
-&IC; user, and contents in it cannot be accessed by the web server without
-&IC; mediating the connection. This directory is generally supposed to 
-only contain directories and Interchange-enabled &glos-HTML; pages,
-nothing else.
-</para><para>
-It is therefore obvious that an alternative way has to be provided
-to serve images. When you define &conf-ImageDir;, &IC; will appropriately
-and transparently prefix all &lt;img src=...&gt; &glos-HTML; tags with
-your value.
-</para><para>
-For example, if the &glos-link-program; and images are kept on the same
-server, and images are found in your web server's document root,
-in the <filename class='directory'>images/</filename> subdirectory, then
-you would set &conf-ImageDir; to <literal>/images/</literal>.
-With this setting in effect, a link such as &lt;img src="order.png"&gt;
-would automatically be translated to &lt;img src="/images/order.png"&gt;.
+A setting of &conf-ImageDir; <literal>/images/</literal> and a specification
+of <literal>&lt;img src="test/test.png"&gt;</literal> would be
+translated to <literal>&lt;img src="/images/test/test.png"&gt;</literal>.
 __END__
 
 __NAME_ notes



1.3                  xmldocs/refs/ImageDirSecure


rev 1.3, prev_rev 1.2
Index: ImageDirSecure
===================================================================
RCS file: /var/cvs/xmldocs/refs/ImageDirSecure,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- ImageDirSecure	6 Nov 2006 18:41:20 -0000	1.2
+++ ImageDirSecure	9 Jan 2009 19:35:50 -0000	1.3
@@ -19,10 +19,10 @@
 <literal>src=</literal> file specifications,
 <emphasis role='bold'>when the originating page is being served
 over a secure connection (HTTPS)</emphasis>.
-To be precise, actually, this setting applies to image locations mentioned in <![CDATA[ <img src="">, <input src="">, <body background="">, <table background=""> and table subelements (<th>, <tr> and <td>).]]>
+This setting applies to image locations mentioned in <![CDATA[ <img src="">, <input src="">, <body background="">, <table background=""> and table subelements (<th>, <tr> and <td>).]]>
 </para><para>
 This is useful if you are using separate HTTPS and HTTP servers, and cannot
-make the image directory path heads match. If &conf-ImageDirSecure; is
+make the image directory paths match. If &conf-ImageDirSecure; is
 unspecified, it defaults to &conf-ImageDir;.
 __END__
 



1.5                  xmldocs/refs/Inet_Mode


rev 1.5, prev_rev 1.4
Index: Inet_Mode
===================================================================
RCS file: /var/cvs/xmldocs/refs/Inet_Mode,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- Inet_Mode	9 May 2008 16:25:07 -0000	1.4
+++ Inet_Mode	9 Jan 2009 19:35:50 -0000	1.5
@@ -26,8 +26,8 @@
 __END__
 
 __NAME__ notes
-You will need &IC; INET mode in only rare circumstances (that is, only if your
-Web and &IC; server are not the same machine).
+In general, you will need &IC; INET mode when the
+Web and &IC; server are not the same machine.
 </para><para>
 The default port number, <literal>7786</literal>, was chosen since it
 represents the ASCII numbers of letters <literal>M</literal> and



1.3                  xmldocs/refs/ItemAction


rev 1.3, prev_rev 1.2
Index: ItemAction
===================================================================
RCS file: /var/cvs/xmldocs/refs/ItemAction,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- ItemAction	2 Jul 2007 12:54:18 -0000	1.2
+++ ItemAction	9 Jan 2009 19:35:50 -0000	1.3
@@ -40,14 +40,13 @@
 <emphasis role='bold'>will not</emphasis> cause this function to be invoked. The
 triggers only fire when the cart contents are modified through the standard
 Interchange &glos-CGI;-based variable processing. Therefore, it is assumed
-(for the moment, at least) that any programmer sufficiently comfortable or
+that any programmer sufficiently comfortable or
 confident to manipulate cart contents directly can also be given the
 responsibility of deciding whether or not it is appropriate to manually invoke
 this function.
 </para><para>
 This &glos-configuration; directive is very similar to &conf-CartTrigger;
-and &conf-CartTriggerQuantity;, the two directives that could be percieved
-as more recent and flexible options.
+and &conf-CartTriggerQuantity;, the two more recent and flexible options.
 __END__
 
 __NAME__ example: Specifying __FILENAME__



1.15                 xmldocs/refs/Jobs


rev 1.15, prev_rev 1.14
Index: Jobs
===================================================================
RCS file: /var/cvs/xmldocs/refs/Jobs,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -r1.14 -r1.15
--- Jobs	3 Apr 2008 15:39:10 -0000	1.14
+++ Jobs	9 Jan 2009 19:35:50 -0000	1.15
@@ -15,9 +15,10 @@
 __NAME__ description
 </para><para>
 This directive configures Interchange batch &glos-jobs; facility.
-It accepts a list of key/value pairs.
+For detailed discussion, please see the &glos-jobs; glossary entry.
 </para><para>
-It can be specified at both the global and &glos-catalog; level.
+The directive accepts a list of key/value pair and
+can be specified at both global and &glos-catalog; level.
 </para><para>
 The available keys for the <emphasis role='bold'>global directive</emphasis>
 are:
@@ -34,18 +35,18 @@
 <row>
 <entry><literal>MaxLifetime</literal></entry>
 <entry><literal>600</literal></entry>
-<entry>The maximum time (in seconds) that a job will be allowed to run.</entry>
+<entry>The maximum time in seconds that a job will be allowed to run</entry>
 </row>
 <row>
 <entry><literal>MaxServers</literal></entry>
 <entry><literal>1</literal></entry>
-<entry>The maximum number of servers processing jobs. Excess jobs will be queued.
+<entry>The maximum number of servers processing jobs. Excess jobs will be queued
 </entry>
 </row>
 <row>
 <entry><literal>UseGlobal</literal></entry>
 <entry><literal>false</literal></entry>
-<entry>Search always for global job definitions.
+<entry>Always search for global job definitions?
 </entry>
 </row>
 </tbody>
@@ -70,20 +71,20 @@
 <entry><literal>add_session</literal></entry>
 <entry><literal>false</literal></entry>
 <entry>Add session dump to 
-<olink targetdoc='glossary' targetptr='JobOutput'>job output</olink>.</entry>
+<olink targetdoc='glossary' targetptr='JobOutput'>job output</olink>?</entry>
 </row>
 <row>
 <entry><literal>autoend</literal></entry>
-<entry><emphasis>None</emphasis></entry>
+<entry>None</entry>
 <entry>
-A macro executed after each invidiual file in the job.
+A macro to execute after each invidiual file in the job
 </entry>
 </row>
 <row>
 <entry><literal>autoload</literal></entry>
-<entry><emphasis>None</emphasis></entry>
+<entry>None</entry>
 <entry>
-A macro executed before each invidiual file in the job.
+A macro to execute before each invidiual file in the job
 </entry>
 </row>
 <row>
@@ -94,65 +95,65 @@
 </row>
 <row>
 <entry><literal>email</literal></entry>
-<entry><emphasis>None</emphasis></entry>
+<entry>None</entry>
 <entry>Email <olink targetdoc='glossary' targetptr='JobOutput'>job output</olink>
-to this address.</entry>
+to this address</entry>
 </row>
 <row>
 <entry><literal>extra_headers</literal></entry>
-<entry><emphasis>None</emphasis></entry>
-<entry>Additional email headers.</entry>
+<entry>None</entry>
+<entry>Additional email headers</entry>
 </row>
 <row>
 <entry><literal>from</literal></entry>
 <entry>&conf-MailOrderTo;</entry>
-<entry>"From" address in emails.</entry>
+<entry>"From" address in emails</entry>
 </row>
 <row>
 <entry><literal>ignore_errors</literal></entry>
 <entry><literal>false</literal></entry>
 <entry>Excludes fatal errors from
-<olink targetdoc='glossary' targetptr='JobOutput'>job output</olink>.
+<olink targetdoc='glossary' targetptr='JobOutput'>job output</olink>
 </entry>
 </row>
 <row>
 <entry><literal>filter</literal></entry>
 <entry>&filter-strip;</entry>
-<entry>Filter(s) applied to
-<olink targetdoc='glossary' targetptr='JobOutput'>job output</olink>.</entry>
+<entry>Filters applied to
+<olink targetdoc='glossary' targetptr='JobOutput'>job output</olink></entry>
 </row>
 <row>
 <entry><literal>initialize</literal></entry>
-<entry><emphasis>None</emphasis></entry>
+<entry>None</entry>
 <entry>
-A macro executed before the job commences.
+A macro executed before the job commences
 </entry>
 </row>
 <row>
 <entry><literal>log</literal></entry>
-<entry><emphasis>None</emphasis></entry>
+<entry>None</entry>
 <entry>Write <olink targetdoc='glossary' targetptr='JobOutput'>job output</olink>
-to this logfile.</entry>
+to this logfile</entry>
 </row>
 <row>
 <entry><literal>subject</literal></entry>
 <entry><literal>Interchange results for job: %s</literal></entry>
-<entry>Subject for emails, including placeholder for job name.</entry>
+<entry>Subject for emails, including placeholder for job name</entry>
 </row>
 <row>
 <entry><literal>suffix</literal></entry>
-<entry><emphasis>None</emphasis></entry>
-<entry>Restrict job to files matching the specified suffix.</entry>
+<entry>None</entry>
+<entry>Restrict job to files matching the specified suffix</entry>
 </row>
 <row>
 <entry><literal>trackdb</literal></entry>
-<entry><emphasis>None</emphasis></entry>
-<entry>Table for <olink targetdoc='glossary' targetptr='JobTracking'>tracking jobs</olink>.</entry>
+<entry>None</entry>
+<entry>Table for <olink targetdoc='glossary' targetptr='JobTracking'>tracking jobs</olink></entry>
 </row>
 <row>
 <entry><literal>use_global</literal></entry>
 <entry><literal>false</literal></entry>
-<entry>Search for global job definitions.</entry>
+<entry>Search for global job definitions?</entry>
 </row>
 </tbody>
 </tgroup>
@@ -170,7 +171,7 @@
 and will return the shell prompt before the jobs have actually started
 executing.
 </para><para>
-A common temporary &glos-session; (<mv>mv_tmp_session</mv> == &glos-true;)
+In that case, a common temporary &glos-session; (<mv>mv_tmp_session</mv> == &glos-true;)
 will be created for use by all of the files
 in the job queue. The session will be closed when the jobs complete.
 The remote IP address will be set to <literal>none</literal> and the
@@ -178,13 +179,10 @@
 __END__
 
 __NAME__ example: Define catalog-level Jobs directive
-Specify directory that will hold the job files, and set up a log file to
-for job runs. Also specify an email address to which any output jobs
-output will be sent:
 <programlisting>
 Jobs &lt;&lt;EOJ
-  base_directory  jobs
   log             logs/jobs.log
+  base_directory  jobs
   email           root@&def-hostname;
 EOJ
 </programlisting>



1.2                  xmldocs/refs/Levies


rev 1.2, prev_rev 1.1
Index: Levies
===================================================================
RCS file: /var/cvs/xmldocs/refs/Levies,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- Levies	6 Nov 2006 22:04:40 -0000	1.1
+++ Levies	9 Jan 2009 19:35:50 -0000	1.2
@@ -1,5 +1,5 @@
 __NAME__ purpose
-specify Levy sections to apply
+specify levy sections to apply
 __END__
 
 



1.2                  xmldocs/refs/Levy


rev 1.2, prev_rev 1.1
Index: Levy
===================================================================
RCS file: /var/cvs/xmldocs/refs/Levy,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- Levy	6 Nov 2006 22:04:40 -0000	1.1
+++ Levy	9 Jan 2009 19:35:50 -0000	1.2
@@ -77,4 +77,5 @@
 descriptions
 turn list into NAME (SYNOPSIS, default DEF) - DESC
 add examples
+description of all levy keys
 __END__



1.6                  xmldocs/refs/Limit


rev 1.6, prev_rev 1.5
Index: Limit
===================================================================
RCS file: /var/cvs/xmldocs/refs/Limit,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- Limit	15 Feb 2008 18:24:50 -0000	1.5
+++ Limit	9 Jan 2009 19:35:50 -0000	1.6
@@ -14,7 +14,7 @@
 <tbody>
 <row>
 <entry>cart_quantity_per_line</entry>
-<entry>-</entry>
+<entry>none</entry>
 <entry>maximum quantity per item in cart</entry>
 </row>
 <row>
@@ -98,3 +98,7 @@
 __NAME__ see also
 RobotLimit
 __END__
+
+__NAME__ missing
+fill in complete limits table
+__END__



1.17                 xmldocs/refs/Locale


rev 1.17, prev_rev 1.16
Index: Locale
===================================================================
RCS file: /var/cvs/xmldocs/refs/Locale,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -r1.16 -r1.17
--- Locale	7 Sep 2007 10:03:23 -0000	1.16
+++ Locale	9 Jan 2009 19:35:50 -0000	1.17
@@ -16,7 +16,7 @@
 <literal>currency_symbol</literal> - default currency symbol. Can be a simple value like "<literal>$</literal>" or " <literal>E</literal>", or a more flexible setting such as '<literal>&lt;img src="euro.png" /&gt;</literal>'.
 </para></listitem>
 <listitem><para>
-<literal>frac_digits</literal> - 
+<literal>frac_digits</literal> -
 </para></listitem>
 <listitem><para>
 <literal>int_curr_symbol</literal> -



1.3                  xmldocs/refs/LocaleDatabase


rev 1.3, prev_rev 1.2
Index: LocaleDatabase
===================================================================
RCS file: /var/cvs/xmldocs/refs/LocaleDatabase,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- LocaleDatabase	6 Nov 2006 18:41:20 -0000	1.2
+++ LocaleDatabase	9 Jan 2009 19:35:50 -0000	1.3
@@ -26,3 +26,6 @@
 </programlisting>
 __END__
 
+__NAME__ missing
+example of LocaleDatabase structure (what fields etc.?)
+__END__



1.2                  xmldocs/refs/LogFile


rev 1.2, prev_rev 1.1
Index: LogFile
===================================================================
RCS file: /var/cvs/xmldocs/refs/LogFile,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- LogFile	6 Nov 2006 22:04:40 -0000	1.1
+++ LogFile	9 Jan 2009 19:35:50 -0000	1.2
@@ -17,7 +17,7 @@
 it is treated relative to the catalog root directory (&glos-CATROOT;).
 </para><para>
 The file will gather output of the
-<function>::logData()</function> function.
+<function>::logData()</function> function (including the tag &tag-log;).
 __END__
 
 __NAME__ see also



1.3                  xmldocs/refs/Mall


rev 1.3, prev_rev 1.2
Index: Mall
===================================================================
RCS file: /var/cvs/xmldocs/refs/Mall,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- Mall	6 Nov 2006 18:41:20 -0000	1.2
+++ Mall	9 Jan 2009 19:35:50 -0000	1.3
@@ -25,7 +25,7 @@
 
 __NAME__ example: Enabling Mall
 <programlisting>
-Mall 1
+Mall Yes
 </programlisting>
 __END__
 



1.2                  xmldocs/refs/MasterHost


rev 1.2, prev_rev 1.1
Index: MasterHost
===================================================================
RCS file: /var/cvs/xmldocs/refs/MasterHost,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- MasterHost	6 Nov 2006 22:04:40 -0000	1.1
+++ MasterHost	9 Jan 2009 19:35:50 -0000	1.2
@@ -8,20 +8,10 @@
 
 __NAME__ description
 This directive specifies the hostname or IP &glos-regexp; that the
-incoming requests must match in order to be allowed access to directories
-protected by non-zero-length <filename>.access</filename> file.
-</para><para>
-For more about this form of access control, see 
-&glos-gate; glossary entry.
+incoming requests must match in order to be allowed access to protected
+directories (see &glos-gate; &GE;), databases and administrative functions.
 __END__
 
-__NAME__ notes
-As you might remember, directories containing file
-<filename>.access</filename> of non-zero bytes in length are accessible only
-to clients matching &conf-MasterHost; or &conf-RemoteUser;.
-__END__
-
-
 __NAME__ example: Defining __FILENAME__
 <programlisting>
 MasterHost 127\.0\.0\.1



1.5                  xmldocs/refs/MaxQuantityField


rev 1.5, prev_rev 1.4
Index: MaxQuantityField
===================================================================
RCS file: /var/cvs/xmldocs/refs/MaxQuantityField,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- MaxQuantityField	26 Jun 2008 09:02:36 -0000	1.4
+++ MaxQuantityField	9 Jan 2009 19:35:50 -0000	1.5
@@ -9,19 +9,12 @@
 
 
 __NAME__ synopsis
-<group choice='plain' rep='repeat'>
-	<arg choice='plain'>
-		[=?]<replaceable>table</replaceable>:<replaceable>column</replaceable>
-	</arg>
-	<arg choice='plain'>
-		[=?]<replaceable>column</replaceable>
-	</arg>
-</group>
+<group choice='opt'><arg choice='plain'>=</arg><arg choice='plain'>?</arg></group><arg choice='opt'><replaceable>table</replaceable>:</arg><arg choice='plain'><replaceable>column</replaceable></arg>
 __END__
 
 
 __NAME__ description
-The &conf-__FILENAME__; directive specifies the &glos-database;s
+The &conf-__FILENAME__; directive specifies &glos-database;s
 and database columns containing the maximum allowed order quantity
 for an item.
 </para><para>
@@ -38,7 +31,7 @@
 all quantities
 found.
 </para><para>
-As of Jun 26, 2008, a field prefixed with <literal>=</literal> overrides
+As of &IC; 5.7.0, a field prefixed with <literal>=</literal> overrides
 any previous value, while a field prefixed with <literal>?</literal>
 overrides previous value only if the new value is greater than zero.
 __END__



1.2                  xmldocs/refs/MimeType


rev 1.2, prev_rev 1.1
Index: MimeType
===================================================================
RCS file: /var/cvs/xmldocs/refs/MimeType,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- MimeType	23 May 2008 23:51:52 -0000	1.1
+++ MimeType	9 Jan 2009 19:35:50 -0000	1.2
@@ -22,7 +22,7 @@
 
 __NAME__ example: Defining __FILENAME__
 <programlisting><![CDATA[
-MimeType itl text/html
+MimeType itl text/plain
 
 MimeType default text/plain
 ]]></programlisting>



1.2                  xmldocs/refs/MoreDB


rev 1.2, prev_rev 1.1
Index: MoreDB
===================================================================
RCS file: /var/cvs/xmldocs/refs/MoreDB,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- MoreDB	9 Jul 2007 11:11:47 -0000	1.1
+++ MoreDB	9 Jan 2009 19:35:50 -0000	1.2
@@ -18,7 +18,7 @@
 This eliminates the need to have a &conf-ScratchDir; directory
 between all &IC; server nodes.
 </para><para>
-This directive can only be used with DBI (database) sessions; trying
+This directive can only be used with DBI (database) &glos-session;s; trying
 to use it with non-database sessions will cause errors.
 __END__
 







More information about the docs mailing list