[docs] xmldocs - docelic modified 22 files

docs at icdevgroup.org docs at icdevgroup.org
Tue Nov 9 17:02:01 EST 2004


User:      docelic
Date:      2004-11-09 22:02:01 GMT
Modified:  glossary rotated-banner tab-delimited
Added:     glossary CSS GET HTML ICROOT MIME SMTP deref js scratch
Added:              weighted
Removed:   glossary css dereferencing get html icroot javascript mime
Removed:            scratch-var smtp weighted-system
Log:
- Adjusting file names with glossary item ID

Revision  Changes    Path
1.3       +1 -1      xmldocs/glossary/rotated-banner


rev 1.3, prev_rev 1.2
Index: rotated-banner
===================================================================
RCS file: /var/cvs/xmldocs/glossary/rotated-banner,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- rotated-banner	20 Oct 2004 15:44:35 -0000	1.2
+++ rotated-banner	9 Nov 2004 22:02:01 -0000	1.3
@@ -1,5 +1,5 @@
 
-<glossentry id="rotated_banner">
+<glossentry id="rotated-banner">
 <glossterm>Rotated banner</glossterm>
 
 <glossdef>



1.2       +1 -1      xmldocs/glossary/tab-delimited


rev 1.2, prev_rev 1.1
Index: tab-delimited
===================================================================
RCS file: /var/cvs/xmldocs/glossary/tab-delimited,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- tab-delimited	15 Oct 2004 20:54:56 -0000	1.1
+++ tab-delimited	9 Nov 2004 22:02:01 -0000	1.2
@@ -1,5 +1,5 @@
 
-<glossentry id="tab_delimited">
+<glossentry id="tab-delimited">
 <glossterm>TAB-delimited data</glossterm>
 
 <glossdef>



1.1                  xmldocs/glossary/CSS


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

<glossentry id="CSS">
<acronym>CSS</acronym>
<glossterm>Cascading Style Sheets</glossterm>

<glossdef>
<para>
<ulink url='http://www.w3.org/Style/CSS/'>CSS</ulink> resource
at &W3C;.
</para>
</glossdef>

</glossentry>



1.1                  xmldocs/glossary/GET


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

<glossentry id="GET">
<glossterm>GET</glossterm>
<glossterm>GET Form Method</glossterm>

<glossdef>
<para>
"GET" resource at 
<ulink url="http://www.cs.tut.fi/~jkorpela/forms/methods.html">Yukka
Korpela's</ulink> website and
<ulink url="http://www.faqs.org/docs/htmltut/forms/_FORM_METHOD_GET.html">
faqs.org</ulink>.
</para>

</glossdef>

</glossentry>




1.1                  xmldocs/glossary/HTML


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

<glossentry id="HTML">
<acronym>HTML</acronym>
<glossterm>HyperText Markup Language</glossterm>

<glossdef>
<para>
<ulink url='http://www.w3.org/MarkUp/'>HTML</ulink> resource at &W3C;.
</para>
</glossdef>

</glossentry>



1.1                  xmldocs/glossary/ICROOT


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

<glossentry id="ICROOT">
<glossterm>ICROOT</glossterm>
<glossterm>Interchange Root Directory</glossterm>

<glossdef>
<para>
</para>

</glossdef>

</glossentry>




1.1                  xmldocs/glossary/MIME


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

<glossentry id="MIME">
<acronym>MIME</acronym>
<glossterm>Multipurpose Internet Mail Extensions</glossterm>

<glossdef>
<para>
<ulink url='http://www.mhonarc.org/~ehood/MIME/'>MIME</ulink> resource.
</para>
</glossdef>

</glossentry>




1.1                  xmldocs/glossary/SMTP


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

<glossentry id="SMTP">
<acronym>SMTP</acronym>
<glossterm>Simple Mail Transfer Protocol</glossterm>

<glossdef>
<para>
<ulink url='http://cr.yp.to/smtp.html'>SMTP</ulink> resource.
</para>
<para>
<classname>Net::SMTP</classname> <ulink url="http://search.cpan.org/~gbarr/">Perl module</ulink> (follow the "libnet" link).
</para>
</glossdef>

</glossentry>




1.1                  xmldocs/glossary/deref


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

<glossentry id="deref">
<glossterm>Dereferencing</glossterm>

<glossdef>
<para>
<emphasis>Dereferencing</emphasis> is strictly a computer-programming
issue, but we will try to explain it in very brief and comprehensible terms,
so that you understand the idea of <firstterm>dereferencing</firstterm> and
its practical effect when data structures are copied.
</para><para>
Let's say we want to compose a list of a few automobiles. Each entry 
in the list will contain the fields
<database class='field'>model</database>,
<database class='field'>year</database> and
<database class='field'>mileage</database>.
</para><para>
Theoretically speaking, to solve this real-world problem with the help of a
computer, we would create a template (containing the three fields), and
produce one <emphasis>instance</emphasis> of the template for each car
we add to our list. (How this list is created, how the elements are added
and how they relate to each other is irrelevant here).
</para><para>
One imaginary list with three instances could be visually represented
in the following way:
</para>
<programlisting>
             Model     Year  Mileage
  list[0] { 'Fiat',    1996, 177940 }
  list[1] { 'Citroen', 2001, 66000  }
  list[2] { 'Citroen', 2002, 23000  }
</programlisting>

<para>
There is only one copy of this list in computer memory, and we read or modify
the elements by obtaining <firstterm>references</firstterm>
(or, <firstterm>pointers</firstterm>) to appropriate entries.
</para><para>
If we take <literal>list</literal> above to contain the list of references
to the entries, we can 
use <literal>list[0].Model</literal> to retrieve the value "Fiat", or
<literal>list[2].Year</literal> to retrieve "2002". For both of those fields,
a reference was first <emphasis>dereferenced</emphasis> (or,
<emphasis>followed</emphasis>) to reach the actual data fields.
</para><para>
When list elements need to be copied to another location (usually as part of
some bigger plan which, again, we are not interested in), they can be copied
<emphasis>by value</emphasis> (with dereferencing) or
<emphasis>by reference</emphasis> (obviously, without dereferencing).
In former case, you would end up with 2 references and 2 different
lists (initially they would be the same but afterwards you could modify
each with no connection to the other). In the latter case, you would again
have 2 references, but both pointing to the same list. Modifying data through
any of the two references would have impact on both.
</para><para>
So, when a data structure (or its element) is said to be copied
<emphasis>without dereferencing</emphasis>, then in case it was a reference,
it is still copied in itself, but all copies point to the same location.
</para>

</glossdef>

</glossentry>




1.1                  xmldocs/glossary/js


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

<glossentry id="js">
<glossterm>JavaScript</glossterm>

<glossdef>
<para>
</para>
</glossdef>

</glossentry>




1.1                  xmldocs/glossary/scratch


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

<glossentry id="scratch">
<glossterm>Scratch variables</glossterm>
<glossterm>Scratch space</glossterm>
<glossterm>Scratchpad</glossterm>

<!--<acronym></acronym>-->
<!--<abbrev></abbrev>-->

<glossdef>
<para>
To each new visitor, Interchange assigns an unique
<firstterm>session ID</firstterm> and (among other things) creates a
<firstterm>scratch space</firstterm> (also referred to as 
the <emphasis>scratchpad</emphasis>) to hold various variables
which are valid throughout the session.
</para>
<para>
Once defined, a scratch variable will exist either until it is explicitly
deleted, or the session terminates.
</para>
<para>
The catalog programmer has complete control over the scratch variables.
The following tags manipulate the scratch space:
<tag>set</tag>,
<tag>seti</tag>,
<tag>tmp</tag>,
<tag>tmpn</tag>,
<tag>scratch</tag>,
<tag>scratchd</tag>,
</para>
<para>
Scratch variables are also used in form processing. See the 
<tag>button</tag> tag for examples.
</para>

</glossdef>

</glossentry>




1.1                  xmldocs/glossary/weighted


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

<glossentry id="weighted">
<glossterm>weighted</glossterm>

<!--<acronym></acronym>-->
<!--<abbrev></abbrev>-->

<glossdef>
<para>
meek.
</para>

</glossdef>

</glossentry>









More information about the docs mailing list