docs/diploma

changeset 211:f2b8481789f6

better diagrams and other small changes
author meillo@marmaro.de
date Sun, 04 Jan 2009 10:28:40 +0100
parents 2181dc39ec06
children bbbaf7b328f8
files thesis/tex/2-MarketAnalysis.tex thesis/tex/3-MailTransferAgents.tex thesis/tex/4-MasqmailsFuture.tex thesis/tex/6-NewDesign.tex
diffstat 4 files changed, 18 insertions(+), 21 deletions(-) [+]
line diff
     1.1 --- a/thesis/tex/2-MarketAnalysis.tex	Sun Jan 04 10:27:30 2009 +0100
     1.2 +++ b/thesis/tex/2-MarketAnalysis.tex	Sun Jan 04 10:28:40 2009 +0100
     1.3 @@ -26,24 +26,18 @@
     1.4  
     1.5  Figure \ref{fig:comm-classification} shows a classification of communication technologies sorted by the properties synchronous/asynchronous and written/recorded. Email and \NAME{SMS} are written and asynchronous communication; \NAME{IM} and chats are written information too, but synchronous. Recorded information are voice mail and video messages as examples for asynchronous communication. VoIP is an example for synchronous communication.
     1.6  
     1.7 -One might be surprised to find Instant \emph{Messaging} not in the group of \emph{message} communication. Instant Messaging could be put in both groups because it allows asynchronous communication additional to being a chat system. The reasons why it is sorted to dialog communication are its primary use for dialog communication and the very fast---instant---delivery time.
     1.8 -
     1.9 -Email is not limited to written information, at least since the advent of \NAME{MIME}, which allows to include multimedia content in textual email messages. Thus recorded information can be sent as sub parts of emails. The same applies to Instant Messaging too, where file transfer is an additional sub service offered by most systems. In general recorded information can be transmitted in an encoded textual form.
    1.10 -
    1.11 -
    1.12 -
    1.13 -\input{kvmacros}
    1.14 -\kvunitlength=3cm
    1.15 -\kvnoindex
    1.16 -
    1.17 -\begin{figure} %fixme: table or figure?
    1.18 +\begin{figure}
    1.19  	\begin{center}
    1.20 -		\input{input/comm-classification.tex}
    1.21 +		\includegraphics[scale=0.75]{img/comm-classification.eps}
    1.22  	\end{center}
    1.23  	\caption{Classification of electronic communication}
    1.24  	\label{fig:comm-classification}
    1.25  \end{figure}
    1.26  
    1.27 +One might be surprised to find Instant \emph{Messaging} not in the group of \emph{message} communication. Instant Messaging could be put in both groups because it allows asynchronous communication additional to being a chat system. The reasons why it is sorted to dialog communication are its primary use for dialog communication and the very fast---instant---delivery time.
    1.28 +
    1.29 +Email is not limited to written information, at least since the advent of \NAME{MIME}, which allows to include multimedia content in textual email messages. Thus recorded information can be sent as sub parts of emails. The same applies to Instant Messaging too, where file transfer is an additional sub service offered by most systems. In general recorded information can be transmitted in an encoded textual form.
    1.30 +
    1.31  
    1.32  
    1.33  
    1.34 @@ -52,16 +46,16 @@
    1.35  
    1.36  The current position on the life cycle of the introduced communication technologies is depicted in figure \ref{fig:comm-lifecycle}. It is important to notice that there is no time line matching for all of them---some life cycles are shorter than others---the shape of the graph, however, is the same.
    1.37  
    1.38 -Video messages and voice mail are technologies in the introduction phase. Voice over \NAME{IP} is heavily growing these days. Instant Messaging has reached maturation, but still growing. Email is an example for a technology in the saturation phase. Declining does none of the above mentioned; telefax is an example for a declining technology.
    1.39 -
    1.40  \begin{figure}
    1.41  	\begin{center}
    1.42 -		\input{input/comm-lifecycle.tex}
    1.43 +		\includegraphics[scale=0.75]{img/comm-lifecycle.eps}
    1.44  	\end{center}
    1.45  	\caption{Life cycle of electronic communication technologies}
    1.46  	\label{fig:comm-lifecycle}
    1.47  \end{figure}
    1.48  
    1.49 +Video messages and voice mail are technologies in the introduction phase. Voice over \NAME{IP} is heavily growing these days. Instant Messaging has reached maturation, but still growing. Email is an example for a technology in the saturation phase. Declining does none of the above mentioned; telefax is an example for a declining technology.
    1.50 +
    1.51  Email ranges in the saturation phase, which is defined by a saturated market, no more products are needed, there is no more growth. This means, email is a technology used by everyone who want to use it. It is a standard technology. The current form of email in the current market is on the top of its life cycle. The future is decline, sooner or later.
    1.52  
    1.53  But life cycles positions change as the subject or the market changes. An examples is the \name{Flash} animation software. The product's change from a drawing and animation system to a technology for website building, advertising, and movie distribution, and the then changing target market, made it slip back on the life cycle. If the email system would evolve to become the basis for Unified Messaging (see section \ref{sec:unified-messaging}), a similar slip back would be the consequence. An example for a changing market are the \NAME{DVD} standards \NAME{DVD+} and \NAME{DVD$-$}. With the upcoming next generation formats BlueRay and \NAME{HD-DVD}, a much sooner decline of \NAME{DVD+} and \NAME{DVD$-$} started, even before reaching their last development steps in storage size. Such can happen to email too, if Unified Messaging is a revolution to the email system instead of an evolution.
    1.54 @@ -159,7 +153,8 @@
    1.55  
    1.56  \begin{figure}
    1.57  	\begin{center}
    1.58 -		\input{input/email-swot.tex}
    1.59 +		%\input{input/email-swot.tex}
    1.60 +		\includegraphics[scale=0.75]{img/email-swot.eps}
    1.61  	\end{center}
    1.62  	\caption{\NAME{SWOT} analysis for email}
    1.63  	\label{fig:email-swot}
     2.1 --- a/thesis/tex/3-MailTransferAgents.tex	Sun Jan 04 10:27:30 2009 +0100
     2.2 +++ b/thesis/tex/3-MailTransferAgents.tex	Sun Jan 04 10:28:40 2009 +0100
     2.3 @@ -97,7 +97,7 @@
     2.4  
     2.5  \subsection{The four major Free Software MTAs}
     2.6  
     2.7 -Now follows a small introduction to the five programs chosen for comparison, except \masqmail\ which already was introduced in chapter \ref{chap:introduction}. Longer introductions, including analysis and comparison, were written by Jonathan de \person{Boyne Pollard} \cite{jdebp}.
     2.8 +Now follows a small introduction to the five programs chosen for comparison, except \masqmail\ which already was introduced in chapter \ref{chap:introduction}. Longer introductions, including analysis and comparison, were written by Jonathan \person{de Boyne Pollard} \cite{jdebp}.
     2.9  
    2.10  
    2.11  
    2.12 @@ -176,7 +176,7 @@
    2.13  \subsubsection*{Architecture}
    2.14  
    2.15  Architecture is most important when comparing \MTA{}s. Many other properties of a program depend on its architecture. %fixme: add ref?
    2.16 -Munawar \person{Hafiz} \cite{hafiz05} discusses in detail on \mta\ architecture, comparing \sendmail, \qmail, \postfix, and \name{sendmail X}. Jonathan de \person{Boyne Pollard}'s \MTA\ review \cite{jdebp} is a source too.
    2.17 +Munawar \person{Hafiz} \cite{hafiz05} discusses in detail on \mta\ architecture, comparing \sendmail, \qmail, \postfix, and \name{sendmail X}. Jonathan \person{de Boyne Pollard}'s \MTA\ review \cite{jdebp} is a source too.
    2.18  
    2.19  Two different architecture types show off: monolithic and modular \mta{}s.
    2.20  
     3.1 --- a/thesis/tex/4-MasqmailsFuture.tex	Sun Jan 04 10:27:30 2009 +0100
     3.2 +++ b/thesis/tex/4-MasqmailsFuture.tex	Sun Jan 04 10:28:40 2009 +0100
     3.3 @@ -305,7 +305,8 @@
     3.4  
     3.5  \begin{figure}
     3.6  	\begin{center}
     3.7 -		\input{input/masqmail-arch.tex}
     3.8 +		%\input{input/masqmail-arch.tex}
     3.9 +		\includegraphics[scale=0.75]{img/callgraph.eps}
    3.10  	\end{center}
    3.11  	\caption{Call graph of \masqmail\ to show its internal structure}
    3.12  	\label{fig:masqmail-arch}
    3.13 @@ -385,7 +386,7 @@
    3.14  
    3.15  Security, extendability, and the other quality properties appear to have crucial importance in this decision. If they are important for future versions of \masqmail, a new design is a must.
    3.16  
    3.17 -\person{Graff} and \person{van Wyk} describe the situation best: ``[I]n today's world, your software is likely to have to operate in a very hostile security environment.'' \cite{graff05} An old-fashioned \mta\ depends, for sure, on a dieing branch, called \name{trusted envrironments}. And nothing other than a fresh and better design will help to survive.
    3.18 +\person{Graff} and \person{van Wyk} describe the situation best: ``[I]n today's world, your software is likely to have to operate in a very hostile security environment.'' \cite{graff03} An old-fashioned \mta\ depends, for sure, on a dieing branch, called \name{trusted envrironments}. And nothing other than a fresh and better design will help to survive.
    3.19  
    3.20  The suggested further development on \masqmail\ is: First add the most needed features, being authentication and encryption, to the current code base. This is the short time goal. Second---and this is the long time goal---design a new architecture that satisfies the requirements identified, especially the quality requirements. The implementation of this design shall then, after being usable and throughoutly tested, superseed the old \masqmail.
    3.21  
     4.1 --- a/thesis/tex/6-NewDesign.tex	Sun Jan 04 10:27:30 2009 +0100
     4.2 +++ b/thesis/tex/6-NewDesign.tex	Sun Jan 04 10:28:40 2009 +0100
     4.3 @@ -2,6 +2,7 @@
     4.4  
     4.5  The last sections identified the jobs that need to be done by a modern \MTA; problems and prefered choices were mentioned too. Now the various jobs are assigned to modules, of which an architecture is created. It is inpired by existing ones and driven by the identified jobs and requirements.
     4.6  
     4.7 +``Many times in life, getting off to the right start makes all the difference.'' \cite[page~32]{graff03}
     4.8  
     4.9  
    4.10  
    4.11 @@ -209,7 +210,7 @@
    4.12  
    4.13  \begin{figure}
    4.14  	\begin{center}
    4.15 -		\input{input/masqmail-arch-new.tex}
    4.16 +		\includegraphics[width=\textwidth]{img/masqmail-arch-new.eps}
    4.17  	\end{center}
    4.18  	\caption{A new designed architecture for \masqmail}
    4.19  	\label{fig:masqmail-arch-new}