mirrors/arti.git/crates/tor-proto/src/stream/ctrl.rs, branch arti-v1.4.3mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.4.32025-02-20T20:15:12Ztor-proto: Add a tunnel module.2025-02-20T20:15:12ZDavid Gouletdgoulet@torproject.org2025-02-13T16:58:04Zurn:sha1:31ee1dbbe88f92d99d66614d0625cb6e87d48edd
Move StreamTarget to the tunnel module and the circuit module.
From now on streams will be implemented on tunnels, not circuits.
This moves `StreamTarget` to the tunnel module. A future change will
replace `ClientCirc` with `ClientTunnel` inside `StreamTarget`.
This is mostly code motion, best reviewed with `--color-moved`.
Signed-off-by: David Goulet <dgoulet@torproject.org>
proto: Clarify applicability of ClientStreamCtrl.2025-01-30T15:30:54ZNick Mathewsonnickm@torproject.org2025-01-30T15:30:54Zurn:sha1:f90b57cd7d84ed5bb955b0f3e39569c4ec1603d9Add "TODO RPC" notes around DataStreamCtrl per review.2023-05-24T19:25:33ZNick Mathewsonnickm@torproject.org2023-05-24T19:24:23Zurn:sha1:e4758a754ec06cd6fc071f46aff3b5da892fd558proto: Create a `DataStreamCtrl` type.2023-05-22T15:27:44ZNick Mathewsonnickm@torproject.org2023-05-22T15:15:14Zurn:sha1:0df0cf425032ff05d0d405d82436cbfd86faf3ac
The idea here is that we want to make DataStream visible to the
RPC system without requiring that the RPC session hold the
DataStream itself (or the Reader, or the Writer). We could solve
this problem by making _all_ the state in the DataStream shared,
but that would introduce unnecessary extra locking in our critical
path.
Instead we're creating the notion of a "control handle" that lets
you manage and observe a stream without actually owning the stream.
Right now the only supported functionality is asking for the
stream's circuit.
Part of #847