[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[tor-bugs] #12506 [BridgeDB]: Separate BridgeDB databases from distributors
#12506: Separate BridgeDB databases from distributors
-------------------------------------------------+-------------------------
Reporter: isis | Owner: isis
Type: enhancement | Status: new
Priority: major | Milestone:
Component: BridgeDB | Version:
Keywords: bridgedb-dist, bridgedb-db, | Actual Points:
bridgedb-1.0.x | Points:
Parent ID: |
-------------------------------------------------+-------------------------
What was originally called "BridgeDB" is essentially two very different
systems, which should be kept separate, and should be runnable on separate
machines:
1. BridgeDB descriptor parsers, databases, and hashrings.
This part of BridgeDB's system takes the bridge descriptor files
received from the BridgeAuthority (Tonga), parses them, shoves them into
databases, and assigns them to the hashrings of the various bridge
distributors.
2. BridgeDB distributors.
This part of BridgeDB's system distributes the bridges to clients,
using various mechanisms. This would currently be the
`bridgedb.Dist.EmailDistributor` which replies to email requests for
bridges, and the `bridgedb.Dist.IPBasedDistributor` which runs the
[https://bridges.torproject.org web interface]. Each distributor listens
for clients' requests and responds with bridges from that distributor's
hashring, as appropriate.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/12506>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs