diff options
authorOlli Salli <>2012-06-18 18:09:10 (GMT)
committerOlli Salli <>2012-06-18 18:11:21 (GMT)
commite34916960343a5ab83ef7bf362b91f15840a65f1 (patch)
parenteabb2ac50aab83c70c5684570583b45591ee222a (diff)
Final tidy-up from browsing through and seeing that it looks consistent
Ready for print \o/
-rw-r--r--asyncfactory.diabin2910 -> 2904 bytes
3 files changed, 11 insertions, 11 deletions
diff --git a/asyncfactory.dia b/asyncfactory.dia
index 3acee18..5fff6bc 100644
--- a/asyncfactory.dia
+++ b/asyncfactory.dia
Binary files differ
diff --git a/gradu.tex b/gradu.tex
index c1cbfc2..9a2ce14 100644
--- a/gradu.tex
+++ b/gradu.tex
@@ -465,7 +465,7 @@ with an object of another class.
Object state is represented by \emph{member variables}. The data members of \mbox{SIMULA} objects
can be directly accessed anywhere (\cite{dahl1967simula}, Chapter 7). In fact, it's possible to
-usefully declare pure data classes that contain no other actions than acccess~\cite{dahletal68}.
+usefully declare pure data classes that contain no other actions than access~\cite{dahletal68}.
Liskov and Zilles argued \cite{liskov74} that the abstract semantics and available operations should
define a data type, not the internal representation of its state. Accordingly, the principal
difference between their concept of \emph{operation clusters} and \mbox{SIMULA} classes is that
@@ -1282,7 +1282,7 @@ with state are exported.
\caption{Shapiro's proxy pattern}
@@ -1484,7 +1484,7 @@ architecture.
In a centralized architecture, both interest registration and guaranteed delivery are implemented by
-a specific process, or an abstract load-balancing collection of processes~\cite{okietal93}. The
+a specific process, or an abstract load-balancing collection of proces-ses~\cite{okietal93}. The
parties communicating in the system connect to this central service with point-to-point links
\cite{eugsteretal03}. By connecting relevant publishers and subscribers together, such an entity
however provides the illusion of a shared bus topology \cite{okietal93}. This construction is
@@ -1793,7 +1793,7 @@ routing services. The structure of this case is illustrated in Figure~\ref{fig:d
\caption{D-Bus bus topology}
@@ -1919,8 +1919,8 @@ intended to be useful for many kinds of applications.
In Section~\ref{subsec:dbus:objmodel} we mentioned that in addition to methods and signals, D-Bus
interfaces may include properties. There is a standard interface, which objects can implement to expose
-access to properties on their other interfaces. This interface, \texttt{org.freedesktop.Properties},
-is presented in Listing~\ref{dbusiface:dbus:props}.
+access to properties on their other interfaces. This interface,
+\texttt{\-desk\-top.Pro\-per\-ties}, is presented in Listing~\ref{dbusiface:dbus:props}.
\dbusmethod{Get}{s:~Interface, s:~Property}{v:~Value}
@@ -2303,7 +2303,7 @@ actually send the message payload on the wire has less of an effect.
\caption{Context switches during D-Bus message delivery}
@@ -3061,7 +3061,7 @@ that only shows the contacts in the address book, or those in a particular chat
\caption{Contact ownership in Telepathy}
diff --git a/ b/
index 1003f5c..b7a5b84 100644
--- a/
+++ b/
@@ -11,7 +11,7 @@ digraph rpcstubs {
{node [label="Algorithm 2", pos="2,0!"] algo2};
{node [shape=record, pos="1,-1!",
- label="{ { <astub> Procedure A client stub | <bstub> Procedure B client stub } | <rpc> RPC runtime }"]
+ label="{ { <astub> Proc. A client stub | <bstub> Proc. B client stub } | <rpc> RPC runtime }"]
algo1 -> clientstubs:astub:n;
@@ -24,9 +24,9 @@ digraph rpcstubs {
{node [fontsize=16]};
{node [shape=record,
- label="{ { Procedure A implementation | Procedure B implementation } | { Procedure A service stub | Procedure B service stub } | <rpc> RPC runtime }"]
+ label="{ { Proc. A impl. | Proc. B impl. } | { Proc. A service stub | Proc. B service stub } | <rpc> RPC runtime }"]
- clientstubs:rpc -> service:rpc [len=6];
+ clientstubs:rpc -> service:rpc [len=5];