mirrors/arti.git/crates/tor-proto/src/client/stream.rs, branch arti-v1.8.0mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.8.02025-10-21T17:08:14Zproto: Fix doc links post-refactoring2025-10-21T17:08:14ZGabriela Moldovangabi@torproject.org2025-10-21T17:08:14Zurn:sha1:1b3104f9dfb31c727d20a2b1f3bb49cf9d083ccfproto: Move dumb pipes to top-lvl stream module2025-10-21T17:08:13ZGabriela Moldovangabi@torproject.org2025-10-21T17:08:13Zurn:sha1:86a5d8ee712a57955f5256ac5af2c2f044a43a61proto: Rename data cmd checkers to {Inbound,Outbound}DataCmdChecker2025-10-16T13:47:15ZGabriela Moldovangabi@torproject.org2025-10-16T12:48:06Zurn:sha1:12d2effc1410f8b59534ab883d727b6844dc14a7
The previous "incoming" terminology was rather ambiguous.
Prompted by https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/3348#note_3275337
proto: Move IncomingDataCmdChecker to top-level stream module.2025-10-16T13:47:15ZGabriela Moldovangabi@torproject.org2025-09-30T00:04:25Zurn:sha1:869d1243cd3b17820fe234b3047e0e2fd8cc406b
This will be used by relays too (for validating incoming messages on
streams).
This is just code motion, so it's best reviewed with `--color-moved`.
proto: Split out DataCmdChecker into multiple types.2025-10-16T13:47:15ZGabriela Moldovangabi@torproject.org2025-09-29T17:58:10Zurn:sha1:38a38a0f46852310057f598c5739b4ab7774be15
The incoming one will be used for the exit relay implementation too.
Also, with this change, receiving `CONNECTED` on an incoming stream will
result in a clearer error message. Previously, the check against
receiving `CONNECTED` on an incoming stream was bundled with the
double-CONNECTED check for client data streams, so in the incoming
stream case, the error message was misleading ("Received CONNECTED twice
on a stream.").
proto: Avoid crate-pub reexports of shared types from the client module.2025-10-16T13:47:15ZGabriela Moldovangabi@torproject.org2025-10-01T14:35:53Zurn:sha1:7045d7b8e1b6f6edf283bc20a9a4a0038ad93acb
This makes it easier to see which parts are implementation-agnostic
(i.e. do not import from crate::client).
proto: Move cmdchecker under top-level stream module.2025-10-16T13:47:15ZGabriela Moldovangabi@torproject.org2025-09-29T17:29:39Zurn:sha1:a3fc3c534db4d4782c22ca2bcbd947812b77bd44
The CmdChecker will be used by relays too, so I am moving it to the
shared `stream` module.
proto: Move flow_ctrl module under stream.2025-10-07T09:31:47ZGabriela Moldovangabi@torproject.org2025-10-01T16:33:10Zurn:sha1:3fcc257517dd8ba4b111364b09237d547ce3c836
This will be used by exits too, so I am moving it out of `client`.
tor-proto: remove a `pub(crate) use` from `client::stream`2025-09-10T04:37:29ZSteven Engleropara@torproject.org2025-09-10T00:55:24Zurn:sha1:0cdf389a1dfec6ee5604004660c5a142356495b2
For internal types, I think it becomes too much of a mess to export
everything through a single module.
tor-proto: reorganize some flow control modules2025-09-10T04:33:37ZSteven Engleropara@torproject.org2025-09-10T00:42:12Zurn:sha1:17ce18f1f530ceb8fd79940773afc86c5dd17461
This is all private (or pub(crate)) code.