[interchange-docs] xmldocs - docelic modified 11 files

docs at icdevgroup.org docs at icdevgroup.org
Sun Jan 11 12:49:45 UTC 2009


User:      docelic
Date:      2009-01-11 12:49:45 GMT
Modified:  refs     PageTableMap ParseVariables Password PermanentDir
Modified:           Pragma PreFork PriceDefault PriceField Profiles
Modified:           Promiscuous
Added:     refs     PreForkSingleFork
Log:
* Updates to P* config directives

Revision  Changes    Path
1.2                  xmldocs/refs/PageTableMap


rev 1.2, prev_rev 1.1
Index: PageTableMap
===================================================================
RCS file: /var/cvs/xmldocs/refs/PageTableMap,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- PageTableMap	3 Apr 2008 16:04:13 -0000	1.1
+++ PageTableMap	11 Jan 2009 12:49:45 -0000	1.2
@@ -2,3 +2,37 @@
 map field names for page lookup tables
 __END__
 
+Revision 2.21: download - view: text, markup, annotated - select for diffs
+Tue Jan 22 02:07:08 2002 UTC (6 years, 11 months ago) by mheins
+Branches: MAIN
+Diff to: previous 2.20: preferred, colored
+Changes since revision 2.20: +10 -2 lines
+
+	* Add new PageTables capability. Includes:
+
+		-- PageTables directive in Config.pm (enables/routes PageTables)
+		-- PageTableMap directive in Config.pm (to map field names)
+		-- Support for database read of pages in Vend::Util::readin
+		-- "Teleport" mode which reads a page as it was/is at a particular
+		   time.
+
+	  This capablity theoretically would work with GDBM databases but
+	  you would never want to use it that way.
+
+	  Basically, if you place a record in the table "PageTables" with a
+	  key of "index", a read of that key in the page table will pre-empt
+	  a read from any PageDir or TemplateDir .
+
+	  If you set Vend::Session->{teleport} to a %Y%h%m%H%M time value,
+	  it will return pages with a show_date earlier than that value
+	  and an expiration date later than that value.  In the case of
+	  a tie, the later show_date wins.
+
+	  PageTableMap allows you to remap field names if desired; not
+	  recommended as UI may not honor mapping to begin with, but
+	  makes remap possible.
+
+	* Move Control space to Vend::Interpolate::Tmp to prevent
+	  storage in session. Also, allows multiple control spaces
+	  to be set up (for nesting).
+



1.4                  xmldocs/refs/ParseVariables


rev 1.4, prev_rev 1.3
Index: ParseVariables
===================================================================
RCS file: /var/cvs/xmldocs/refs/ParseVariables,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- ParseVariables	15 Feb 2008 18:24:50 -0000	1.3
+++ ParseVariables	11 Jan 2009 12:49:45 -0000	1.4
@@ -12,7 +12,7 @@
 
 
 __NAME__ description
-Specify that the &glos-configuration; directives should have their 
+Specify whether the &glos-configuration; directives should have their 
 values parsed (&glos-interpolate;d).
 </para><para>
 This applies to all configuration directives except &conf-Variable;.



1.5                  xmldocs/refs/Password


rev 1.5, prev_rev 1.4
Index: Password
===================================================================
RCS file: /var/cvs/xmldocs/refs/Password,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- Password	15 Feb 2008 18:24:50 -0000	1.4
+++ Password	11 Jan 2009 12:49:45 -0000	1.5
@@ -23,7 +23,7 @@
 using <command>htpasswd</command>, or invoking
 <command>perl -le'print crypt("mypasswd","AA")'</command>,
 where <literal>mypasswd</literal> is the desired password and
-<literal>AA</literal> are your two always random characters called 
+<literal>AA</literal> are two random characters called 
 the &glos-salt;.
 </para><para>
 See &var-MV_NO_CRYPT; and &tag-crypt; for more discussion.



1.5                  xmldocs/refs/PermanentDir


rev 1.5, prev_rev 1.4
Index: PermanentDir
===================================================================
RCS file: /var/cvs/xmldocs/refs/PermanentDir,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- PermanentDir	22 Jan 2008 19:49:17 -0000	1.4
+++ PermanentDir	11 Jan 2009 12:49:45 -0000	1.5
@@ -10,4 +10,8 @@
 <programlisting>
 PermanentDir tmp/perm
 </programlisting>
-__END__
\ No newline at end of file
+__END__
+
+__NAME__ missing
+description
+__END__



1.3                  xmldocs/refs/Pragma


rev 1.3, prev_rev 1.2
Index: Pragma
===================================================================
RCS file: /var/cvs/xmldocs/refs/Pragma,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- Pragma	12 Aug 2006 22:43:11 -0000	1.2
+++ Pragma	11 Jan 2009 12:49:45 -0000	1.3
@@ -37,5 +37,5 @@
 __END__
 
 __NAME__ see also
-pragma
+pragma, tag
 __END__



1.5                  xmldocs/refs/PreFork


rev 1.5, prev_rev 1.4
Index: PreFork
===================================================================
RCS file: /var/cvs/xmldocs/refs/PreFork,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- PreFork	3 Aug 2008 11:03:55 -0000	1.4
+++ PreFork	11 Jan 2009 12:49:45 -0000	1.5
@@ -4,7 +4,7 @@
 
 
 __NAME__ see also
-StartServers
+StartServers, PreForkSingleFork
 __END__
 
 __NAME__ synopsis
@@ -22,11 +22,10 @@
 (or in other words, "start ahead of time") some number of &IC; servers
 that will be ready to serve client requests immediately as they come in.
 </para><para>
-If you're running PreFork, you should always try &conf-PreForkSingleFork; too
-to start. Only turn off &conf-PreForkSingleFork; if something pathological
-happens (the most likely outcome being a slew of zombies piling up that
-are never reaped). Using it successfully creates the absolute minimal
-number of forks necessary.
+If you're running PreFork, you should use it in combination with
+&conf-PreForkSingleFork;, to create the absolute minimal number of forks
+necessary. Only turn &conf-PreForkSingleFork; off 
+if it causes zombie processes to pile up.
 </para><para>
 This method reduces system overhead due to forking and is the fastest and
 best way to run a busy &IC; server.



1.2                  xmldocs/refs/PriceDefault


rev 1.2, prev_rev 1.1
Index: PriceDefault
===================================================================
RCS file: /var/cvs/xmldocs/refs/PriceDefault,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- PriceDefault	6 Nov 2006 22:04:40 -0000	1.1
+++ PriceDefault	11 Jan 2009 12:49:45 -0000	1.2
@@ -1,4 +1,26 @@
+__NAME__ purpose
+specify default price field in chained pricing schemes
+__END__
 
-setira defaultni field kad je specifikacija chained pricinga
-table:field:key i field nije namjesten
+__NAME__ synopsis
+<arg choice='plain'><replaceable>field_name</replaceable></arg>
+__END__
 
+__NAME__ description
+When chained &glos-price; scheme is used and a specification of
+<literal><replaceable>table</replaceable>:<replaceable>field</replaceable>:<replaceable>key</replaceable></literal> is given without explicit
+<literal>:<replaceable>field</replaceable></literal>, the value in
+&conf-__FILENAME__; will be used.
+</para><para>
+The default value is <literal>price</literal>.
+__END__
+
+__NAME__ example: Setting __FILENAME__
+<programlisting>
+__FILENAME__ price
+</programlisting>
+__END__
+
+__NAME__ see also
+PriceField
+__END__



1.4                  xmldocs/refs/PriceField


rev 1.4, prev_rev 1.3
Index: PriceField
===================================================================
RCS file: /var/cvs/xmldocs/refs/PriceField,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- PriceField	6 Nov 2006 18:41:21 -0000	1.3
+++ PriceField	11 Jan 2009 12:49:45 -0000	1.4
@@ -24,9 +24,8 @@
 
 __NAME__ example: Redefining PriceField
 <programlisting>
-PriceField cijena
+PriceField preis
 </programlisting>
-"Cijena", for example, is a croatian equivalent of "price".
 __END__
 
 __NAME__ example: Setting PriceField depending on current locale
@@ -37,7 +36,7 @@
 # Establish locale-specific price field
 Locale fr_FR  PriceField  prix
 </programlisting>
-Just by the way, if &conf-PriceBreaks; is enabled, the
+With the above example, if &conf-PriceBreaks; is enabled, the
 <database class='field'>prix</database> field from the
 <database>pricing</database> database will be used to develop quantity-based
 pricing.



1.4                  xmldocs/refs/Profiles


rev 1.4, prev_rev 1.3
Index: Profiles
===================================================================
RCS file: /var/cvs/xmldocs/refs/Profiles,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- Profiles	6 Nov 2006 18:41:21 -0000	1.3
+++ Profiles	11 Jan 2009 12:49:45 -0000	1.4
@@ -1,5 +1,5 @@
 __NAME__ purpose
-specify files containing OrderProfile and SearchProfile definitions
+specify files containing OrderProfile definitions on a global level
 __END__
 
 
@@ -19,8 +19,8 @@
 
 
 __NAME__ description
-Specify filenames that contain &conf-OrderProfile; and &conf-SearchProfile; 
-definitions.
+Specify filenames that contain &conf-OrderProfile;
+definitions on a global level.
 __END__
 
 



1.2                  xmldocs/refs/Promiscuous


rev 1.2, prev_rev 1.1
Index: Promiscuous
===================================================================
RCS file: /var/cvs/xmldocs/refs/Promiscuous,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- Promiscuous	6 Nov 2006 22:04:40 -0000	1.1
+++ Promiscuous	11 Jan 2009 12:49:45 -0000	1.2
@@ -16,7 +16,7 @@
 
 
 __NAME__ description
-Allow output of &glos-HTML; code from &glos-value; variables.
+Allow output of &glos-HTML; code from &tag-value; tags.
 __END__
 
 __NAME__ notes



1.1                  xmldocs/refs/PreForkSingleFork


rev 1.1, prev_rev 1.0
Index: PreForkSingleFork
===================================================================
__NAME__ purpose
ensure the prefork code path is entirely controllable by the value of PreFork
__END__


__NAME__ see also
StartServers, PreFork
__END__

__NAME__ synopsis
<group choice='plain'>
	<arg choice='plain'>No</arg>
	<arg choice='plain'>Yes</arg>
</group>
__END__


__NAME__ description
This directive affects &IC; behavior in conjunction with
&conf-PreFork;, ensuring the prefork code path is entirely
controllable by the value of &conf-PreFork;.
</para><para>
If you're running PreFork, you should use it in combination with
&conf-PreForkSingleFork;, to create the absolute minimal number of forks
necessary. Only turn &conf-PreForkSingleFork; off 
if it causes zombie processes to pile up.
</para><para>
This method reduces system overhead due to forking and is the fastest and
best way to run a busy &IC; server.
__END__

__NAME__ example: Enabling __FILENAME__
<programlisting>
PreFork yes
PreForkSingleFork yes
</programlisting>
__END__








More information about the docs mailing list