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
EventProcessors waiting at aSequenceBarrierof status changes.Implementors of this interface must provide a single long value that represents their current cursor value.Called by theRingBufferto pre-populate all the events to fill the RingBuffer.Callback interface to be implemented for processing events as they become available in theRingBufferExperimental poll-based interface for the Disruptor.An EventProcessor needs to be an implementation of a runnable that will poll for events from theRingBufferusing the appropriate wait strategy.Implementations translate (write) data representations into events claimed from theRingBuffer.Implementations translate another data representations into events claimed from theRingBufferImplementations translate another data representations into events claimed from theRingBufferImplementations translate another data representations into events claimed from theRingBufferImplementations translate another data representations into events claimed from theRingBufferCallback handler for uncaught exceptions in the event processing cycle of theBatchEventProcessorException thrown when it is not possible to insert a value into the ring buffer without it wrapping the consuming sequences.Implement this interface in yourEventHandlerto be notified when a thread for theBatchEventProcessorstarts and shuts down.Sequence that follows (by wrapping) another sequencePhased wait strategy for waitingEventProcessors on a barrier.Ring based store of reusable entries containing the data representing an event being exchanged between event producer andEventProcessors.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 dependentEventProcessors for processing a data structureCoordinates claiming sequences for access to a data structure while tracking dependentSequencesStrategy employed for makingEventProcessors wait on a cursorSequence.Callback interface to be implemented for processing units of work as they become available in theRingBuffer.AWorkProcessorwraps a singleWorkHandler, effectively consuming the sequence and ensuring appropriate barriers. -
Classes in com.lmax.disruptor used by com.lmax.disruptor.dslClassDescriptionCalled by the
RingBufferto pre-populate all the events to fill the RingBuffer.Callback interface to be implemented for processing events as they become available in theRingBufferAn EventProcessor needs to be an implementation of a runnable that will poll for events from theRingBufferusing the appropriate wait strategy.Implementations translate (write) data representations into events claimed from theRingBuffer.Implementations translate another data representations into events claimed from theRingBufferImplementations translate another data representations into events claimed from theRingBufferImplementations translate another data representations into events claimed from theRingBufferCallback handler for uncaught exceptions in the event processing cycle of theBatchEventProcessorRing based store of reusable entries containing the data representing an event being exchanged between event producer andEventProcessors.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 dependentEventProcessors for processing a data structureStrategy employed for makingEventProcessors wait on a cursorSequence.WorkerPool contains a pool ofWorkProcessors 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
RingBufferusing the appropriate wait strategy.Concurrent sequence class used for tracking the progress of the ring buffer and event processors.