Expand description
Implements Tor’s “stream“s from a client perspective
A stream is an anonymized conversation; multiple streams can be multiplexed over a single circuit.
To create a stream, use crate::circuit::ClientCirc::begin_stream.
§Limitations
There is no fairness, rate-limiting, or flow control.
Structs§
- The read half of a
DataStream
, implementingfutures::io::AsyncRead
. - An anonymized stream over the Tor network.
- DataStreamCtrl
stream-ctrl
An object used to control and monitor a data stream. - The write half of a
DataStream
, implementingfutures::io::AsyncWrite
. - IncomingStream
hs-service
A pending request from the other end of the circuit for us to open a new stream. - IncomingStreamRequestContext
hs-service
Information about a stream request, as passed to anIncomingStreamRequestFilter
. - A ResolveStream represents a pending DNS request made with a RESOLVE cell.
- A set of preferences used to declare how a new stream should be opened.
- The read part of a stream on a particular circuit.
Enums§
- IncomingStreamRequest
hs-service
The allowed incoming messages on anIncomingStream
. - IncomingStreamRequestDisposition
hs-service
What action to take with an incoming stream request. - A preference for IPv4 vs IPv6 addresses; usable as a nicer frontend for BeginFlags.
Traits§
- ClientStreamCtrl
stream-ctrl
An object that lets the owner “control” a client stream. - IncomingStreamRequestFilter
hs-service
A callback that can check whether a given stream request is acceptable immediately on its receipt.