| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | tor-dirmgr: Create a bootstrap-status exporting mechanism. | Nick Mathewson | 2022-01-18 | 1 | -4/+465 |
| | | | | | | | | | | | | | | | | | | | | | | | The interface is similar to the one exposed by `arti-client`: it internally uses postage::watch to give a series of events showing when a bootstrap status is changing. Thanks to the existing state/driver separation in the DirMgr design we don't need much new logic: each download state needs to expose (internally) how far along it is in its download, which the bootstrap code passes to the DirMgr if it has changed. I believe that in the long run, we'll probably want to expose more (or different) information here, and we'll want to process it differently. With that in mind, I've made the API for `DirBootstrapStatus` deliberately narrow, so that we can change its of its internal later on without breaking code that depends on it. (The information exposed by this commit is not yet summarized in `arti-client`.) Part of #96. | ||||
| * | Refactor directory events to use a FlagPublisher mechanism. | Nick Mathewson | 2021-12-14 | 1 | -86/+327 |
| | | | | | | | | | This approach tries to preserve the current interface, but uses a counter-based event backend to implement a coalescing stream of events that can be represented as small integers. The advantage here is that publishing events no longer needs to be a blocking operation, since there is no queue to fill up. | ||||
| * | add semicolons if nothing returned | Daniel Eades | 2021-11-25 | 1 | -1/+1 |
| | | |||||
| * | Notify guard manager on network change and state flush. | Nick Mathewson | 2021-10-10 | 1 | -0/+3 |
| | | |||||
| * | Move all crates into a `crates` subdirectory. | Nick Mathewson | 2021-08-27 | 1 | -0/+118 |
| This will cause some pain for now, but now is really the best time to do this kind of thing. | |||||
