mirrors/arti.git/crates/tor-proto/src/client/stream, branch arti-v1.5.0mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.5.02025-08-28T10:54:48Zproto: Add a circuit module shared between client and relay impls.2025-08-28T10:54:48ZGabriela Moldovangabi@torproject.org2025-08-26T17:48:56Zurn:sha1:4ee5a4abcee895e79588888f6bc8eaa6963a6ba7
This is just code motion (I suggest reviewing with `--color-moved`).
This also moves the implementation-agnostic parts from
`tor_proto::client::circuit` to a new `tor_proto::circuit` module.
tor-proto: don't allow consecutive XOFF messages2025-08-27T18:07:12ZSteven Engleropara@torproject.org2025-08-27T18:05:34Zurn:sha1:1c328624ac5213ff711576b1072022ae63e7c01aproto: Add prop349 note about the resolve stream handler.2025-08-20T16:59:43ZGabriela Moldovangabi@torproject.org2025-08-20T15:16:53Zurn:sha1:b5a9c0048be4cf61fa746f15ad22100b2790608etor-proto: add comments to `CC_XOFF_CLIENT`2025-08-18T21:53:14ZSteven Engleropara@torproject.org2025-08-13T05:00:42Zurn:sha1:93eac258450bf2688044e9a1ec831e06520c0ca9
This tries to explain that the amount of incoming data we choose to
buffer on an arti stream doesn't really matter for arti's socks proxy,
since the amount of data buffered by the kernel is significantly higher.
proto: Move the `stream` module under `client` (breaking).2025-08-18T16:09:04ZGabriela Moldovangabi@torproject.org2025-08-18T15:52:38Zurn:sha1:702e7276898d3f31e22033c5b64fea91703f3701
The `stream` module is client-specific, for the most part, so I am
moving it under `client`. Later on, we will factor out the parts that
can be shared with the relay implementation.
Note: this is a breaking change as the deleted `stream` module was
`pub`. We could've kept the module and reexported from it the public
types from `tor_proto::client::stream`, but I think it's better to have
this `client` namespacing, because it makes the separation between the
client and relay parts clearer.