[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

[tor-commits] [torspec/master] Describing CONN_BW's ConnType



commit c77a39e5655e7ba10f50cb9c19d4b0153780bbf8
Author: Damian Johnson <atagar@xxxxxxxxxxxxxx>
Date:   Sun Nov 3 10:44:33 2013 -0800

    Describing CONN_BW's ConnType
    
    Our new CONN_BW events' ConnType enumeration is poorly defined...
    
      https://trac.torproject.org/10086
    
    This is just a guess on my part for what it's supposed to be. I have *not*
    trudged through the tor code to puzzle out how it actually allocates this
    enumeration.
---
 control-spec.txt |   10 +++++++++-
 1 file changed, 9 insertions(+), 1 deletion(-)

diff --git a/control-spec.txt b/control-spec.txt
index f84d078..3ae4180 100644
--- a/control-spec.txt
+++ b/control-spec.txt
@@ -2278,7 +2278,15 @@
   The syntax is:
      "650" SP "CONN_BW" SP "ID=" ConnID SP "TYPE=" ConnType
               SP "READ=" BytesRead SP "WRITTEN=" BytesWritten CRLF
-     ConnType = "OR" / "DIR" / "EXIT"
+
+     ConnType = "OR" /  ; Carrying traffic within the tor network. This can
+                          either be our own (client) traffic or traffic we're
+                          relaying within the network.
+                "DIR" / ; Fetching tor descriptor data, or transmitting
+                          descriptors we're mirroring.
+                "EXIT"  ; Carrying traffic between the tor network and an
+                          external destination.
+
      BytesRead = 1*DIGIT
      BytesWritten = 1*DIGIT
 



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