Uses of Package
com.lmax.disruptor
Packages that use com.lmax.disruptor
Package
Description
The Disruptor is a concurrent programming framework for exchanging and coordinating work as a continuous series of events.
-
Classes in com.lmax.disruptor used by com.lmax.disruptorClassDescriptionBase class for the various sequencer types (single/multi).Used to alert
EventProcessor
s waiting at aSequenceBarrier
of status changes.Implementors of this interface must provide a single long value that represents their current cursor value.Called by theRingBuffer
to pre-populate all the events to fill the RingBuffer.Callback interface to be implemented for processing events as they become available in theRingBuffer
Experimental poll-based interface for the Disruptor.An EventProcessor needs to be an implementation of a runnable that will poll for events from theRingBuffer
using the appropriate wait strategy.Implementations translate (write) data representations into events claimed from theRingBuffer
.Implementations translate another data representations into events claimed from theRingBuffer
Implementations translate another data representations into events claimed from theRingBuffer
Implementations translate another data representations into events claimed from theRingBuffer
Implementations translate another data representations into events claimed from theRingBuffer
Callback handler for uncaught exceptions in the event processing cycle of theBatchEventProcessor
Exception thrown when it is not possible to insert a value into the ring buffer without it wrapping the consuming sequences.Implement this interface in yourEventHandler
to be notified when a thread for theBatchEventProcessor
starts and shuts down.Sequence that follows (by wrapping) another sequencePhased wait strategy for waitingEventProcessor
s on a barrier.Ring based store of reusable entries containing the data representing an event being exchanged between event producer andEventProcessor
s.Concurrent sequence class used for tracking the progress of the ring buffer and event processors.Coordination barrier for tracking the cursor for publishers and sequence of dependentEventProcessor
s for processing a data structureCoordinates claiming sequences for access to a data structure while tracking dependentSequence
sStrategy employed for makingEventProcessor
s wait on a cursorSequence
.Callback interface to be implemented for processing units of work as they become available in theRingBuffer
.AWorkProcessor
wraps a singleWorkHandler
, effectively consuming the sequence and ensuring appropriate barriers. -
Classes in com.lmax.disruptor used by com.lmax.disruptor.dslClassDescriptionCalled by the
RingBuffer
to pre-populate all the events to fill the RingBuffer.Callback interface to be implemented for processing events as they become available in theRingBuffer
An EventProcessor needs to be an implementation of a runnable that will poll for events from theRingBuffer
using the appropriate wait strategy.Implementations translate (write) data representations into events claimed from theRingBuffer
.Implementations translate another data representations into events claimed from theRingBuffer
Implementations translate another data representations into events claimed from theRingBuffer
Implementations translate another data representations into events claimed from theRingBuffer
Callback handler for uncaught exceptions in the event processing cycle of theBatchEventProcessor
Ring based store of reusable entries containing the data representing an event being exchanged between event producer andEventProcessor
s.Concurrent sequence class used for tracking the progress of the ring buffer and event processors.Coordination barrier for tracking the cursor for publishers and sequence of dependentEventProcessor
s for processing a data structureStrategy employed for makingEventProcessor
s wait on a cursorSequence
.WorkerPool contains a pool ofWorkProcessor
s that will consume sequences so jobs can be farmed out across a pool of workers.Callback interface to be implemented for processing units of work as they become available in theRingBuffer
. -
Classes in com.lmax.disruptor used by com.lmax.disruptor.utilClassDescriptionAn EventProcessor needs to be an implementation of a runnable that will poll for events from the
RingBuffer
using the appropriate wait strategy.Concurrent sequence class used for tracking the progress of the ring buffer and event processors.