From: Roger Dingledine <arma@torproject.org>
Date: Mon, 24 Mar 2003 03:31:11 +0000 (+0000)
Subject: finish specifying topic flow control
X-Git-Tag: tor-0.0.2pre8~251
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=0dad4999179f730422c543c111a90af148842bdd;p=thirdparty%2Ftor.git

finish specifying topic flow control


svn:r217
---

diff --git a/doc/tor-spec.txt b/doc/tor-spec.txt
index ab729346db..5698d4dfe7 100644
--- a/doc/tor-spec.txt
+++ b/doc/tor-spec.txt
@@ -287,7 +287,7 @@ which reveals the downstream node.
           0: Identity 
           1: Single DES in OFB
           2: RC4
-	  3: Triple DES in OFB
+          3: Triple DES in OFB
 
      The port and address field denote the IPV4 address and port of
      the next onion router in the circuit, or are set to 0 for the
@@ -524,11 +524,12 @@ which reveals the downstream node.
 6.4. Topic flow control
 
    Edge nodes use TOPIC_SENDME data cells to implement end-to-end flow
-   control for individual connections across circuits.  As with circuit
+   control for individual connections across circuits. As with circuit
    flow control, edge nodes begin with a window of cells (500) per
    topic, and increment the window by a fixed value (50) upon receiving
    a TOPIC_SENDME data cell. Edge nodes initiate TOPIC_SENDME data
-   cells when
+   cells when both a) the window is <= 450, and b) there are less than
+   ten cell payloads remaining to be flushed at that edge.
 
 7. Directories and routers