-
Notifications
You must be signed in to change notification settings - Fork 2
/
Copy pathDAPNET 2.0 Software internals.tex
71 lines (57 loc) · 2.18 KB
/
DAPNET 2.0 Software internals.tex
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
\documentclass[a4paper]{report}
%% Language and font encodings
\usepackage[english]{babel}
\usepackage[utf8x]{inputenc}
\usepackage[T1]{fontenc}
%% Sets page size and margins
\usepackage[a4paper,top=3cm,bottom=2cm,left=3cm,right=3cm,marginparwidth=1.75cm]{geometry}
%% Useful packages
\usepackage{amsmath}
\usepackage{graphicx}
\usepackage[colorinlistoftodos]{todonotes}
\usepackage[colorlinks=true, allcolors=blue]{hyperref}
\usepackage{listings,xcolor}
\usepackage{graphicx}
\usepackage{hyperref}
\usepackage{placeins}
\usepackage{framed, color}
\usepackage{fancyvrb}
\setcounter{secnumdepth}{4}
\setcounter{tocdepth}{3}
\setlength{\parindent}{0pt}
\setlength{\parskip}{1ex plus 0.5ex minus 0.2ex}
\lstset{
basicstyle=\footnotesize\ttfamily,
string=[s]{"}{"},
stringstyle=\color{blue},
comment=[l]{:},
commentstyle=\color{black},
}
\begin{document}
\begin{titlepage}
\centering
\includegraphics[width=1\textwidth]{assets/rwth-afu-dapnet-logo.png}
\vspace{2cm}
{\scshape\LARGE DAPNET 2.0 Concept and Interface Definition \par}
\vspace{1cm}
{\Large\itshape
Thomas Gatzweiler, DL2IC\\
Philipp Thiel, DL6PT\\
Marvin Menzerath\\
Ralf Wilke, DH3WR\\
\par}
\vspace{3cm}
{\scshape\Large Last Change: \today\par}
\end{titlepage}
%\maketitle
\begin{abstract}
This is the concept and interface description of the version 2 of the DAPNET. It's purpose in comparison to the first version released is a more robust clustering and network interaction solution to cope with the special requirements of IP connections over HAMNET which means that all network connections have to be considered with a WAN character resulting in unreliable network connectivity. In terms of consistence of the database, "eventually consistence" is considered to be the most reachable. There are "always right" database nodes inside the so called HAMCLOUD. In case of database conflicts, the version inside the HAMCLOUD cluster is always to be considered right.
\end{abstract}
\tableofcontents
\include{1_Introduction}
\include{2_DAPNET_Network_Definition}
\include{3_Internal_Programming_Workflows}
\include{4_External_Programming_Workflows}
\include{5_Setup_and_Installation}
\include{6_Protocol_Definitions}
\end{document}