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.
A DSL-style API for setting up the disruptor pattern around a ring buffer.
Utility classes
-
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.Convenience class for handling the batching semantics of consuming entries from aRingBufferand delegating the available events to anEventHandler.Strategy for handling a rewindableException when processing an event.Implementors of this interface must provide a single long value that represents their current cursor value.Typically used to decouple classes fromRingBufferto allow easier testingCalled 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.A callback used to process eventsIndicates the result of a call toEventPoller.poll(Handler)An EventProcessor needs to be an implementation of a runnable that will poll for events from theRingBufferusing the appropriate wait strategy.Pulls together the low-level data access and sequencing operations ofRingBufferWrite interface forRingBuffer.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.Sequence that follows (by wrapping) another sequencePhased wait strategy for waitingEventProcessors on a barrier.Callback interface to be implemented for processing events as they become available in theRingBufferwith support for throwing aRewindableExceptionwhen an even cannot be processed currently but may succeed on retry.A special exception that can be thrown while using theBatchEventProcessor.The result returned from theBatchRewindStrategythat decides whether to rewind or throw the exceptionRing 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 structureOperations related to the sequencing of items in aRingBuffer.Coordinates claiming sequences for access to a data structure while tracking dependentSequencesCoordinator for claiming sequences for access to a data structure while tracking dependentSequences.Wait strategies may throw this Exception to inform callers that a message has not been detected within a specific time window.Strategy employed for makingEventProcessors wait on a cursorSequence. -
Classes in com.lmax.disruptor used by com.lmax.disruptor.dslClassDescriptionStrategy for handling a rewindableException when processing an event.Called 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 theBatchEventProcessorCallback interface to be implemented for processing events as they become available in theRingBufferwith support for throwing aRewindableExceptionwhen an even cannot be processed currently but may succeed on retry.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 structureWait strategies may throw this Exception to inform callers that a message has not been detected within a specific time window.Strategy employed for makingEventProcessors wait on a cursorSequence. -
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.