mirrors/arti.git/crates/tor-proto/src/client/stream.rs, branch main

proto: Add crate-level exports for two extra stream types (fmt)

2026-06-17T13:38:44Z

Remove unnecessary `doc(cfg(...))` attributes

2025-12-05T02:40:50Z

Fixes part of #2193. (Edits from nickm: I selected the cases here that I could verify were correct from immediate context.) Edited-by: Nick Mathewson

proto: Move raw under top-level stream mod

2025-11-24T16:47:11Z

proto: Move IncomingStream* types to shared module

2025-11-24T16:31:55Z

proto: Fix doc links post-refactoring

2025-10-21T17:08:14Z

proto: Move dumb pipes to top-lvl stream module

2025-10-21T17:08:13Z

proto: Rename data cmd checkers to {Inbound,Outbound}DataCmdChecker

2025-10-16T13:47:15Z

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:15Z

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:15Z

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:15Z

This makes it easier to see which parts are implementation-agnostic (i.e. do not import from crate::client).