| BatchedPreprocessor |
Batching preprocessor that will briefly delay the sending of a message
if it doesn't fill up a full tunnel message, in which case it queues up
an additional flush task.
|
| DummyValidator |
accept everything
|
| FragmentHandler |
Handle fragments at the endpoint of a tunnel, peeling off fully completed
I2NPMessages when they arrive, and dropping fragments if they take too long
to arrive.
|
| FragmentHandler.DefragmentedReceiver |
Receive messages out of the tunnel endpoint.
|
| HopConfig |
Defines the general configuration for a hop in a tunnel.
|
| HopProcessor |
Take a received tunnel message, verify that it isn't a
duplicate, and translate it into what the next hop will
want.
|
| InboundEndpointProcessor |
Receive the inbound tunnel message, removing all of the layers
added by earlier hops to recover the preprocessed data sent
by the gateway.
|
| IVValidator |
Provide a generic interface for IV validation which may be implemented
through something as simple as a hashtable or more a complicated
bloom filter.
|
| PendingGatewayMessage |
Stores all the state for an unsent or partially-sent message
|
| PumpedTunnelGateway |
This is used for all gateways with more than zero hops.
|
| TrivialPreprocessor |
Do the simplest thing possible for preprocessing - for each message available,
turn it into the minimum number of fragmented preprocessed blocks, sending
each of those out.
|
| TunnelCreatorConfig |
Coordinate the info that the tunnel creator keeps track of, including what
peers are in the tunnel and what their configuration is
See PooledTunnelCreatorConfig for the non-abstract class
|
| TunnelDispatcher.Location |
for shouldDropParticipatingMessage()
|
| TunnelGateway |
Serve as the gatekeeper for a tunnel, accepting messages, coallescing and/or
fragmenting them before wrapping them up for tunnel delivery.
|
| TunnelGateway.DelayedFlush |
|
| TunnelGateway.QueuePreprocessor |
|
| TunnelGateway.Receiver |
|
| TunnelGateway.Sender |
|
| TunnelGatewayPumper |
Run through the tunnel gateways that have had messages added to them and push
those messages through the preprocessing and sending process.
|