nihilist/tor
1
0
Fork 0
mirror of https://gitlab.torproject.org/tpo/core/tor.git synced 2024-11-10 21:23:58 +01:00
Code Issues Packages Projects Releases Wiki Activity

correct the spec for the stream_bw event.

Browse Source 
"neonomad" pointed out on or-talk that the order is opposite from the
intuitive order. explain why. we chose to fix the spec rather than the
code because there are controllers like torflow that already expect
the current behavior.
This commit is contained in:
Roger Dingledine 2009-10-10 15:07:37 -04:00
parent 1c62b9d5fa
commit e84dc32cb8
1 changed files with 12 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
doc/spec/control-spec.txt
View File

@ -1597,17 +1597,21 @@
4.1.13. Bandwidth used on an application stream 4.1.13. Bandwidth used on an application stream
The syntax is: The syntax is:
"650" SP "STREAM_BW" SP StreamID SP BytesRead SP BytesWritten CRLF "650" SP "STREAM_BW" SP StreamID SP BytesWritten SP BytesRead CRLF
BytesRead = 1*DIGIT
BytesWritten = 1*DIGIT BytesWritten = 1*DIGIT
BytesRead = 1*DIGIT
BytesRead and BytesWritten are the number of bytes read and written since BytesWritten and BytesRead are the number of bytes written and read
the last STREAM_BW event on this stream. These events are generated about by the application since the last STREAM_BW event on this stream.
once per second per stream; no events are generated for streams that have
not read or written.
These events apply only to streams entering Tor (such as on a SOCKSPort, Note that from Tor's perspective, *reading* a byte on a stream means
TransPort, or so on). They are not generated for exiting streams. that the application *wrote* the byte. That's why the order of "written"
vs "read" is opposite for stream_bw events compared to bw events.
These events are generated about once per second per stream; no events
are generated for streams that have not written or read. These events
apply only to streams entering Tor (such as on a SOCKSPort, TransPort,
or so on). They are not generated for exiting streams.
4.1.14. Per-country client stats 4.1.14. Per-country client stats