org.apache.pekko.remote.transport

An adapter that wraps a transport and provides interception

An SPI layer for abstracting over logical links (associations) created by a pekko.remote.transport.Transport. Handles are responsible for providing an API for sending and receiving from the underlying channel.

To register a listener for processing incoming payload data, the listener must be registered by completing the Promise returned by pekko.remote.transport.AssociationHandle#readHandlerPromise. Incoming data is not processed until this registration takes place.

Transport implementation to be used for testing.

The TestTransport is basically a shared memory between actor systems. The TestTransport could be programmed to emulate different failure modes of a Transport implementation. TestTransport keeps a log of the activities it was requested to do. This class is not optimized for performance and MUST not be used as an in-memory transport in production systems.

An SPI layer for implementing asynchronous transport mechanisms. The Transport is responsible for initializing the underlying transmission mechanism and setting up logical links between transport entities.

Transport implementations that are loaded dynamically by the remoting must have a constructor that accepts a com.typesafe.config.Config and an pekko.actor.ExtendedActorSystem as parameters.