From: Adriana Draghici <adriana008@gmail.com>
Date: Mon, 8 Feb 2010 11:18:38 +0000 (+0200)
Subject: report - added DB diagram
X-Git-Tag: getopt_long~174
X-Git-Url: http://p2p-next.cs.pub.ro/gitweb/?a=commitdiff_plain;h=5ce5464a8722be5c3714040a572d6dc2dab5e1d5;p=cs-p2p-next.git

report - added DB diagram
---

diff --git a/report/clients.tex b/report/clients.tex
deleted file mode 100644
index f8968d3..0000000
--- a/report/clients.tex
+++ /dev/null
@@ -1,10 +0,0 @@
-The log files analysis takes into consideration two open-source implementations of the BitTorrent protocol. 
-The experiments prior to our research evaluated the performances of several BitTorrent clients, 
-as described in \cite{rdeval}. Based on these results we have chosen \textbf{rasterbar libtorrent}, 
-which in the comparison proved to be the fastest solution, and \textbf{Tribler}.
-While libtorrent provided large amounts of output that could be directly used as an example for our parsing system,
-Tribler did not offer any logging information. Therefore, we dedicated part of our research time to 
-modifing Tribler source code in order to obtain the necessary logs.
-
-
-
diff --git a/report/img/DB.png b/report/img/DB.png
new file mode 100644
index 0000000..23bc002
Binary files /dev/null and b/report/img/DB.png differ
diff --git a/report/logarch.tex b/report/logarch.tex
index afd31ce..fab0a19 100644
--- a/report/logarch.tex
+++ b/report/logarch.tex
@@ -8,7 +8,7 @@
 
 \subsection{BitTorrent Messages}
 \subsection{BitTorrent Clients Instrumentation}
-\input{clients.tex}
+\input{logarch/clients.tex}
 \subsection{Parser}
 \subsection{Database}
 \subsection{GUI}
\ No newline at end of file
diff --git a/report/logarch/clients.tex b/report/logarch/clients.tex
new file mode 100644
index 0000000..021c1ac
--- /dev/null
+++ b/report/logarch/clients.tex
@@ -0,0 +1,15 @@
+The log files analysis takes into consideration two open-source implementations of the BitTorrent protocol. 
+The experiments prior to our research evaluated the performances of several BitTorrent clients that offered a command line interface (CLI), as described in \cite{rdeval}. Based on these results we have chosen \textbf{rasterbar libtorrent}, 
+which in the comparison proved to be the fastest solution, and \textbf{Tribler}.
+
+Libtorrent, developed by Rasterbar \cite{libt2} \cite{libt1}, is a C++ library that implements BitTorrent protocol and
+its extensions. It aims to be cpu and memory efficient, easy to use and suitable for many enivornments and platforms.
+Due to its high performance it is used by many BitTorrent applications, like FireTorrent, Deluge, qBitTorrent, SharkTorrent,
+Miro and Hrktorrent \cite{hrk}, the one we chosed to work with. Hrktorrent is a lightweight torrent client written in C++ and it was appropriate for our testing infrastructure because it offered a command line interface.
+
+%[todo : ce versiuni de libtorrent si hrktorrent folosim?]
+%[todo : sa spun ca folosim CLI interface]  
+
+While libtorrent provided large amounts of output that could be directly used as an example for our parsing system,
+Tribler did not offer any logging information. Therefore, we dedicated part of our research time to 
+modifing Tribler source code in order to obtain the necessary logs.
\ No newline at end of file
diff --git a/report/report.bib b/report/report.bib
index f09ed58..832838e 100644
--- a/report/report.bib
+++ b/report/report.bib
@@ -3,4 +3,12 @@
 	author = {Razvan Deaconescu and Razvan Rughinis and Nicolae Tapus},
 	year = {2009}	
 }
-
+@misc{libt1,
+	title = {http://www.rasterbar.com/products/libtorrent/}
+	}
+@misc{libt2,
+	title = {http://libtorrent.rakshasa.no/}
+}
+@misc{hrk,
+	title = {http://50hz.ws/hrktorrent/}
+}