docs/diploma

changeset 361:f75efd59fefd

added a new sentence or so
author meillo@marmaro.de
date Wed, 28 Jan 2009 15:13:38 +0100
parents 056a353b9116
children 0850f0a9dbb3
files thesis/tex/5-Improvements.tex
diffstat 1 files changed, 3 insertions(+), 5 deletions(-) [+]
line diff
     1.1 --- a/thesis/tex/5-Improvements.tex	Wed Jan 28 15:01:35 2009 +0100
     1.2 +++ b/thesis/tex/5-Improvements.tex	Wed Jan 28 15:13:38 2009 +0100
     1.3 @@ -361,7 +361,9 @@
     1.4  
     1.5  The queue is actually two queues and a data pool. The queues store the spool files---unprocessed in \name{incoming} and in complete and valid form in \name{outgoing}. The \name{pool} is the storage of data files, the message bodies of queued messages. The three parts are represented by three directories within the queue path on disk.
     1.6  
     1.7 -The representation of queued files on disk is basically the same as the one in current \masqmail: one file for the envelope and message header information (the ``spool file''), a second file for the message body (the ``data file''). The spool file's internal structure of current \masqmail\ can be remain. Following is a sample spool file. (The first part is the envelope with comments in parenthesis; the second part is the message header.)
     1.8 +The representation of queued files on disk is basically the same as the one in current \masqmail: one file for the envelope and message header information (the ``spool file''), a second file for the message body (the ``data file''). The spool file's internal structure of current \masqmail\ can be remain.
     1.9 +
    1.10 +Following is a sample spool file from current \masqmail. The first part is the envelope and meta information. The annotations in parenthesis are added afterwards to ease the understanding. The second part after the empty line is the message header.
    1.11  
    1.12  \codeinput{input/sample-spool-file.txt}
    1.13  
    1.14 @@ -375,10 +377,6 @@
    1.15  
    1.16  
    1.17  
    1.18 -
    1.19 -
    1.20 -
    1.21 -
    1.22  \subsubsection*{Inter-module communication}
    1.23  
    1.24  Communication between modules is required to exchange data and status information. This is also called ``Inter-process communication'' (short: \NAME{IPC}) because the modules are independent programs in this case and processes are programs in execution.