diff options
| author | Nick Mathewson <nickm@torproject.org> | 2023-10-14 18:52:20 -0400 |
|---|---|---|
| committer | Nick Mathewson <nickm@torproject.org> | 2023-10-14 18:53:18 -0400 |
| commit | 3457b0720834c8347d8318c1080ebc9486d77300 (patch) | |
| tree | b486a3d03fdfae7d98c4e6cf510179cf907c443f /spec/bandwidth-file-spec/implementation-details.md | |
| parent | a331e9f48790ad4beaba1ee443c5ad8b13d3afb4 (diff) | |
| download | torspec-3457b0720834c8347d8318c1080ebc9486d77300.tar.gz torspec-3457b0720834c8347d8318c1080ebc9486d77300.zip | |
Add short IDs for most long section names
I've left off sections that are headings for their whole document.
Diffstat (limited to 'spec/bandwidth-file-spec/implementation-details.md')
| -rw-r--r-- | spec/bandwidth-file-spec/implementation-details.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/spec/bandwidth-file-spec/implementation-details.md b/spec/bandwidth-file-spec/implementation-details.md index 90f84fa..1695793 100644 --- a/spec/bandwidth-file-spec/implementation-details.md +++ b/spec/bandwidth-file-spec/implementation-details.md @@ -4,7 +4,7 @@ <a id="bandwidth-file-spec.txt-2.4.1"></a> -### Writing bandwidth files atomically +### Writing bandwidth files atomically { #write-atomically } To avoid inconsistent reads, implementations SHOULD write bandwidth files atomically. If the file is transferred from another host, it SHOULD be @@ -19,13 +19,13 @@ Torflow does not write bandwidth files atomically. <a id="bandwidth-file-spec.txt-2.4.2"></a> -### Additional KeyValue pair definitions +### Additional KeyValue pair definitions { #key-value-pairs } KeyValue pairs in RelayLines that current implementations generate. <a id="bandwidth-file-spec.txt-2.4.2.1"></a> -#### Simple Bandwidth Scanner +#### Simple Bandwidth Scanner { #sbws } sbws RelayLines contain these keys: |