[docs] xmldocs - docelic modified 4 files

docs at icdevgroup.org docs at icdevgroup.org
Tue Dec 14 17:24:43 EST 2004


User:      docelic
Date:      2004-12-14 22:24:43 GMT
Modified:  glossary false true
Added:     glossary tracking
Added:     refs     TrackFile
Log:
- Fixed some glossary element texts
- Documented TrackFile. One item every day and it's a success ;-)

Revision  Changes    Path
1.3       +2 -1      xmldocs/glossary/false


rev 1.3, prev_rev 1.2
Index: false
===================================================================
RCS file: /var/cvs/xmldocs/glossary/false,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- false	20 Oct 2004 15:44:35 -0000	1.2
+++ false	14 Dec 2004 22:24:42 -0000	1.3
@@ -1,6 +1,7 @@
 
 <glossentry id="false">
-<glossterm>False value</glossterm>
+<glossterm>false</glossterm>
+<glossterm>false value</glossterm>
 
 <glossdef>
 <para>



1.3       +2 -1      xmldocs/glossary/true


rev 1.3, prev_rev 1.2
Index: true
===================================================================
RCS file: /var/cvs/xmldocs/glossary/true,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- true	20 Oct 2004 15:44:35 -0000	1.2
+++ true	14 Dec 2004 22:24:43 -0000	1.3
@@ -1,6 +1,7 @@
 
 <glossentry id="true">
-<glossterm>True value</glossterm>
+<glossterm>true</glossterm>
+<glossterm>true value</glossterm>
 
 <glossdef>
 <para>



1.1                  xmldocs/glossary/tracking


rev 1.1, prev_rev 1.0
Index: tracking
===================================================================

<glossentry id="tracking">
<glossterm>tracking</glossterm>
<glossterm>user tracking</glossterm>

<glossdef>
<para>
Several actions performed by users are recorded by &IC;'s usertracking 
facility, if one is enabled. Usertrack data can actually be obtained from two
different locations.
</para><para>
The first location is &IC; itself, where you tune the &conf-TrackFile;
directive to your needs (such as <filename>logs/usertrack</filename>).
This is the approach used in the &std-catalog; demo.
</para><para>
The second location are the HTTP headers. You can configure the Web server to
write this header into access logs; here's an example for the &APACHE;
web server:

<programlisting><![CDATA[
LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\" \
			%T %v \"%{X-Track}o\"" track
CustomLog /var/log/apache/track.log track
]]></programlisting>
</para>

</glossdef>

</glossentry>




1.1                  xmldocs/refs/TrackFile


rev 1.1, prev_rev 1.0
Index: TrackFile
===================================================================
__NAME__ purpose
user tracking log filename
__END__


__NAME__ synopsis
<group choice='req'>
	<arg choice='plain'>file name</arg>
</group>
__END__


__NAME__ description
Specify the <emphasis>usertrack</emphasis> log file location. 
</para><para>
User &glos-tracking; can be used in back office administration to summarize
traffic by affiliates.
</para><para>
The Interchange daemon must have the permission to create and write to the
specified file.
__END__

__NAME__ example: Setting TrackFile
<programlisting>
TrackFile /var/log/interchange/track.log
</programlisting>
__END__









More information about the docs mailing list