vecna
/
lox
mirror of https://gitlab.torproject.org/vecna/lox.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Update README to account for these changes

This commit is contained in:
onyinyang 2023-06-23 12:46:38 -04:00
parent 607466b949
commit 12921bfcd0
No known key found for this signature in database
GPG Key ID: 156A6435430C2036
1 changed files with 1 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
README.md
View File

@ -29,12 +29,8 @@ These changes are necessary to keep the consistentcy of bridges in buckets that
bridge should not be distributed. Since we do not know if the results of bridge should not be distributed. Since we do not know if the results of
these tests indicate a blocking event, we are allowing for bridges that these tests indicate a blocking event, we are allowing for bridges that
rdsys marks as `gone` to be updated without penalty in the Lox library. rdsys marks as `gone` to be updated without penalty in the Lox library.
4. The above has led to some additional changes to the `BridgeTable` structure 4. The vectors within `bridge_table.rs` have been refactored into HashMaps that use a unique `u32` for lookup. This will be backed by some kind of persistent storage prior to deployment.
that can be found in [`crates/lox-library/src/bridge_table.rs`](https://gitlab.torproject.org/tpo/anti-censorship/lox-rs/-/blob/main/crates/lox-library/src/bridge_table.rs) and include a `recyclable` field that indicates indexes within the bucket vector that can be reused and `unallocated_bridges` which account for left-over bridges that are eligible to be assigned but were left over when the total number of bridges % `MAX_BRIDGES_PER_BUCKET` is not 0.
In the near future, the vectors within `bridge_table.rs` will likely be
refactored into maps that use a bridge's fingerprint for lookup. This will
be backed by some kind of persistent storage prior to deployment.
#### lox-distributor #### lox-distributor