1.1 --- a/thesis/tex/4-MasqmailsFuture.tex	Sun Jan 04 10:27:30 2009 +0100
     1.2 +++ b/thesis/tex/4-MasqmailsFuture.tex	Sun Jan 04 10:28:40 2009 +0100
     1.3 @@ -305,7 +305,8 @@
     1.4  
     1.5  \begin{figure}
     1.6  	\begin{center}
     1.7 -		\input{input/masqmail-arch.tex}
     1.8 +		%\input{input/masqmail-arch.tex}
     1.9 +		\includegraphics[scale=0.75]{img/callgraph.eps}
    1.10  	\end{center}
    1.11  	\caption{Call graph of \masqmail\ to show its internal structure}
    1.12  	\label{fig:masqmail-arch}
    1.13 @@ -385,7 +386,7 @@
    1.14  
    1.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.
    1.16  
    1.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.
    1.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.
    1.19  
    1.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.
    1.21