package net.i2p.client.streaming.impl
Implementation of a TCP-like (reliable, authenticated, in order) set of sockets for communicating over the IP-like (unreliable, unauthenticated, unordered) I2P messages.
This is the streaming implementation. For the API (which you probably want), see net.i2p.client.streaming. Clients should not need to access anything in this package directly.
Note that this class is split across two jars, streaming.jar and ministreaming.jar. The interfaces and some code are in ministreaming.jar, but the real work gets done in streaming.jar. Clients must have both jars in their classpath.
Most clients will require (only) streaming.jar, ministreaming.jar, and i2p.jar in their classpath to communicate with the router.
See also: RFC 2140 (TCP congestion control) • RFC 5681 (congestion control) • RFC 6298 (RTO computation).
- ClassDescriptionMaintain the state controlling a streaming connection between two destinations.Verdict of one floor evaluation.One
Connection.getWindowCeiling()cache entry: ceiling + sample time as a single atomically-published value (see the field's Javadoc).Receive data from the MessageOutputStream, build a packet, and send it through a connection.Used if no new packet was sent.Failed write status.Receive new connection attemptsSimple end-of-queue marker.Accept-queue bookkeeping for one enqueued SYN.Coordinate all of the connections for a single local destination.The callback interface for a pong.Holds the state for a pending ping request, including optional payload and notification callback.Wrapper for a pooled connection with metadata.Encapsulates a connection rejection reason with an optional Retry-After duration in seconds.Outcome of evaluating one SYN burst-gate trip against the dest's recorded strike.A recorded SYN-burst strike, and how many distinct burst windows this dest has tripped inside the current strike window.Define the current options for the con (and allow custom tweaking midstream).RTT initialization state machine.Receive a packet for a particular connection - placing the data onto the queue, marking packets as acked, updating various fields, etc.Count how often we have received an incoming connection This offers basic DOS protection but is not a complete solution.Bridge to allow accepting new connections.Bridge between the full streaming lib and the I2PSocket API.Centralize the coordination and multiplexing of the local client's streaming.Define the configuration for streaming and verifying data on the socket.Receive raw information from the I2PSession and turn it into Packets, if we can.InputStream implementation that accepts messages arriving out of order and presents the data in proper sequence for reading.An OutputStream implementation that buffers data and forwards it to aMessageOutputStream.DataReceiverin chunks upon buffer full or flush.Interface for receiving data flushed from this stream.Interface to detect status of an asynchronous write operation.This contains solely the data that goes out on the wire, including the local and remote port which is embedded in the I2CP overhead, not in the packet itself.Dispatch inbound stream packets to a small pool of single-threaded shard workers, so a slow or hostile connection no longer stalls the session notifier thread for every other connection on the same destination.Queue element: keeps the already-resolved connection with its packet.Process one dispatched (connection, packet) pair.Handles incoming packets by dispatching them to the appropriate connection, server socket, or responding with a reset (RST) packet if no valid connection is found.This is the class used for outbound packets.Queue out packets to be sent through the session.Write a standard pcap file with a "TCP" packet that can be analyzed with standard tools such as wireshark.Builder for TCP option blocks in the pcap output.Per-destination timer for scheduling packet retransmissions.Examine a connection's state and pick the right scheduler for it.Scheduler used for after both sides have had their close packets ACKed, but the final timeout hasn't passed.Scheduler used for after both SYNs have been ACKed and both sides have closed the stream, but either we haven't ACKed their close or they haven't ACKed ours.Scheduler used for after our SYN has been sent and ACKed but one (or more) sides haven't closed the stream yet.Scheduler used once we've sent our SYN but it hasn't been ACKed yet.Scheduler used for after the final timeout has passed or the connection was reset.Scheduler used after we've locally done a hard disconnect, but the final timeout hasn't passed.Base class for connection state schedulers.Scheduler used for locally created connections where we have not yet sent the initial SYN packet.Scheduler used after receiving an inbound connection but before we have sent our own SYN.A Westwood+ bandwidth estimator with a first stage anti-aliasing low pass filter based on RTT, and the time-varying Westwood filter based on inter-arrival time.Bridge to I2PServerSocket.Bridge to I2PSocket.Coordinates what we do 'next'.Share important TCP Control Block parameters across Connections to the same remote peer.We attempted to have more open streams than we are willing to put up with.