mirrors/arti.git/crates/tor-proto/src/stream/data.rs, branch arti-v1.4.5mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.4.52025-06-26T17:33:36Ztor-proto: Renamed `DataReaderState::Ready` to `Open`2025-06-26T17:33:36ZSteven Engleropara@torproject.org2025-06-26T17:33:36Zurn:sha1:c4f15fab9a79bfb12b71e06a2e2ac0eb7af16766tor-proto: remove unneeded `DataReaderState::ReadingCell` state2025-06-26T17:03:13ZSteven Engleropara@torproject.org2025-06-26T04:52:17Zurn:sha1:71e10a6155b533436befb205661fe98b83fab9e6
Now that we no longer need to store a future, there's no need for this
state since we're never pending waiting for a future to complete.
tor-proto: rework `StreamReceiver` into a `futures::Stream`2025-06-26T17:03:13ZSteven Engleropara@torproject.org2025-06-26T04:45:27Zurn:sha1:3eabc89dc9a1f6be166c2a468785d7708aa3a5bb
Having this be a `futures::Stream` makes it nicer to work with. For
example we are able to remove a boxed future from `DataReaderState`,
which should be better for performance and makes the code simpler.
As mentioned in a previous commit when this type was named
`StreamReader`, this type is public in the API, but is not actually
accessible. As far as I can tell there is no way to construct it or
access it.
tor-proto: rename `StreamReader` to `StreamReceiver`2025-06-26T17:01:22ZSteven Engleropara@torproject.org2025-06-26T03:20:38Zurn:sha1:d633fbc26e84b190306998833f5c8a1e10b58e50
In rust, the typical nomenclature is to use "receiver" for channels, and
"reader" for byte streams. For example `mpsc::Receiver` for something
that returns objects and `AsyncRead` for something that reads bytes.
Since we also have a `DataReader` for reading bytes, I think renaming
this from `StreamReader` to `StreamReceiver` better describes what it is
(it's not a "reader" in the typical `Read`/`AsyncRead` sense).
This type is public in the API, but is not actually accessible. As far
as I can tell there is no way to construct it or access it.
tor-proto: use `DynamicRateLimitedWriter` in `DataWriter`2025-06-16T19:19:37ZSteven Engleropara@torproject.org2025-06-09T16:46:37Zurn:sha1:993486444b83d9be21a046a9c04a1efe90a55f3a
This uses just a placeholder `Empty` stream for config updates.
tor-proto: improve `TokioAsyncWrite` compat impl2025-06-16T19:19:37ZSteven Engleropara@torproject.org2025-06-09T16:42:12Zurn:sha1:14b49bfd2f037728d7f02994abb986f0e4301515
We want the tokio trait to call into the futures trait, rather than
having each trait duplicate the logic of calling into the inner writer.
This is less error-prone.
tor-proto: change `wake_when_bytes_available` to `NonZero<u64>`2025-06-08T23:24:31ZSteven Engleropara@torproject.org2025-06-08T21:42:29Zurn:sha1:9779de7adbe4aa9cc848e685151a6c5cde0a7bcetor-proto: change `RateLimitedWriter` logic to use user-configurable limit2025-06-05T15:27:43ZSteven Engleropara@torproject.org2025-06-04T21:23:24Zurn:sha1:71deeccda0f8f253651516bc480861c48e90eab3
The user now sets a constant amount of bytes to wait for.
tor-proto: add `{TokenBucket,RateLimitedWriter}Config` types2025-06-05T15:14:50ZSteven Engleropara@torproject.org2025-06-04T18:51:21Zurn:sha1:03c5c523039a03fe2b479fc9e7f2841440eb529btor-proto: add missing doc comment to `DataWriter::writer`2025-06-05T15:14:50ZSteven Engleropara@torproject.org2025-05-27T19:12:59Zurn:sha1:fc229c050bcc8966d83a802e7a0b929882f4ec61