aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2010-07-30 18:55:24 -0400
committerNick Mathewson <nickm@torproject.org>2010-07-30 18:55:24 -0400
commit6f45101327592333dcc54e08800fbc2cb68ccd49 (patch)
tree6ed550c89289a454c4436fc9facec1d7de206b8d /doc
parent15424bf800a56007d802db3a9d3fe40fbdf2bee5 (diff)
downloadtor-6f45101327592333dcc54e08800fbc2cb68ccd49.tar
tor-6f45101327592333dcc54e08800fbc2cb68ccd49.tar.gz
Clear cell queues when marking or truncating a circuit.
At best, this patch helps us avoid sending queued relayed cells that would get ignored during the time between when a destroy cell is sent and when the circuit is finally freed. At worst, it lets us release some memory a little earlier than it would otherwise. Fix for bug #1184. Bugfix on 0.2.0.1-alpha.
Diffstat (limited to 'doc')
-rw-r--r--doc/spec/tor-spec.txt4
1 files changed, 3 insertions, 1 deletions
diff --git a/doc/spec/tor-spec.txt b/doc/spec/tor-spec.txt
index f448f6da2..5283442fe 100644
--- a/doc/spec/tor-spec.txt
+++ b/doc/spec/tor-spec.txt
@@ -595,7 +595,9 @@ see tor-design.pdf.
To tear down part of a circuit, the OP may send a RELAY_TRUNCATE cell
signaling a given OR (Stream ID zero). That OR sends a DESTROY
cell to the next node in the circuit, and replies to the OP with a
- RELAY_TRUNCATED cell.
+ RELAY_TRUNCATED cell. If the OR has any RELAY cells queued on the
+ circuit for the next node in that it had not yet sent, it MAY
+ drop them without sending them.
When an unrecoverable error occurs along one connection in a
circuit, the nodes on either side of the connection should, if they