summaryrefslogtreecommitdiff
path: root/arti/src/proxy.rs
Commit message (Collapse)AuthorAgeFilesLines
* Use full suite of warnings in arti crate as well.Nick Mathewson2021-05-241-1/+1
|
* Remove tor-proto exposure in tor-client API.Nick Mathewson2021-05-181-8/+8
|
* Add unseparated_literal_suffix lint, and fix it.Nick Mathewson2021-05-031-1/+1
|
* Move timer functions into an extension trait.Nick Mathewson2021-04-171-2/+1
|
* Move around the public modules in tor_rtcompat.Nick Mathewson2021-04-171-1/+1
|
* Remove all non-runtime methods in tor_rtcompat.Nick Mathewson2021-04-161-8/+14
|
* Add a "Runtime" parameter to all the manager types.Nick Mathewson2021-04-161-2/+3
| | | | | This is a big change, but it is a step towards our goal of removing tor_rtcompat:: calls directly.
* rtcompat: Make TLS functionality use Runtime traits.Nick Mathewson2021-04-161-5/+1
| | | | | Now there is nothing in principle that you couldn't access from a Runtime implementation.
* Make incoming Streams of TcpStream a real type for each backend.Nick Mathewson2021-04-161-5/+2
| | | | | This makes things a little more complicated for AsyncStd, and a little simpler for Tokio.
* Port tor_rtcompat::net to use Runtime objects.Nick Mathewson2021-04-161-9/+15
|
* rtcompat: rename traits module to impl_traits.Nick Mathewson2021-04-161-1/+1
|
* Fix Rust-1.51 clippy warnings about acronyms in camel case.Nick Mathewson2021-03-291-6/+6
| | | | This is painful, but we shouldn't have to do it again.
* Move stream timeout logic into tor-client.Nick Mathewson2021-03-241-3/+4
| | | | | | | | | | This is consistent with the other pieces of tor-proto, which do not handle timeouts on their own. It also lets us remove tor-rtcompat as a dependency from tor-proto, and simplify some of the test cases to use async_test. This commit unindents a lot of test code; use git's "-b" flag to read the parts that matter.
* Refactor tokio implpementation in tor-rtcompat.Nick Mathewson2021-03-231-19/+6
| | | | | | | | | | | Now other crates don't need any 'ifdef tokio' code, since there are wrappers that implement 'futures' right. Technically, the 'futures' traits are in some ways less good than the tokio ones, but we need a consistent API if we want to support WASM someday and keep support for async_std. I'd rather hold out hope for a future version of futures::io working like tokio than to fix ourselves into the tokioverse forever.
* Move our command-line interface into a new crate called "arti".Nick Mathewson2021-03-171-0/+237
Closes #106