[tor-commits] [tech-reports/master] Add Rob van der Hoeven's HAR suggestion.

[karsten@xxxxxxxxxxxxxx]

commit c3d7124b3880117c5c064876401f9dedfe7e367c
Author: Karsten Loesing <karsten.loesing@xxxxxxx>
Date:   Tue Sep 24 13:43:36 2013 +0200

    Add Rob van der Hoeven's HAR suggestion.
---
 2013/torperf2/torperf2.tex |   13 +++++++++++--
 1 file changed, 11 insertions(+), 2 deletions(-)

diff --git a/2013/torperf2/torperf2.tex b/2013/torperf2/torperf2.tex
index 1fe89ec..d67bd62 100644
--- a/2013/torperf2/torperf2.tex
+++ b/2013/torperf2/torperf2.tex
@@ -217,8 +217,17 @@ requests.%
 Deciding which data to store should be the responsibility of whoever
 designs a Torperf experiment, though formats should be somewhat uniform
 between experiments.
-A possible results data format could be JSON, but other data formats are
-plausible, too.
+A possible results data format could be based on JSON,%
+\footnote{In particular, we could use a de-facto standard like the HAR
+(HTTP Archive) format to store measurements results.
+Advantages are that such a format is widely used and that there are a lot
+of off-the-shelve tools that can process this format.
+Disadvantages are that such a format captures a lot of meta data that are
+not relevant to us, and that we'd have to add tor-specific data fields to
+the format which wouldn't be processed by existing tools.
+Note that we could use such a format only for request data, not for
+tor-specific data like building circuits and attaching streams.}
+but other data formats are plausible, too.
 
 \subsubsection{Results web interface}
 



_______________________________________________
tor-commits mailing list
tor-commits@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits