io.reactors.protocol.BackpressureProtocols
Backpressure
Related Doc:
package BackpressureProtocols
Represents an established backpressure link.
Represents an established backpressure link.
Connection clients must manually release events from the associated event buffer
and then send pressure tokens back to the producer. The event buffer has an
available signal used to notify about event availability.
For convenience, every backpressure link can be converted into a Pump
object, which automatically sends backpressure tokens when events are dequeued
from the event buffer.
type of the events delivered on the backpressure channel
backpressure channel, used by consumers to signal the producers when additional events can be sent
event buffer that holds events ready to be delivered
resources associated with the link
Abstracts over the underlying two-way communication protocol.
Abstracts over the underlying two-way communication protocol.
Captures the protocol needed to create a two-way server, and to connect to it.
Captures the specific backpressure policy.
Captures the specific backpressure policy.
While the overall picture with backpressure is that producers can only send events to consumers once consumers send them pressure tokens, there are subtle differences in how this backpressure can be implemented. The details are captured in:
Valve object is created from a two-way link on the
producer-side (i.e. client-side).
A variant of a backpressure server that emits backpressure pumps.
A variant of a backpressure server that emits backpressure pumps.
See Backpressure.Server.
Represents the state of a backpressure link server.
Represents the state of a backpressure link server.
type of the request object used by the underlying medium
type of the events delivered on the backpressure channel
request channel that allows the clients to send requests for new backpressure links
server-side event stream that emits links that are established with this backpressure server
resources associated with the backpressure server