Uses of Package
com.lmax.disruptor
-
Packages that use com.lmax.disruptor Package Description com.lmax.disruptor The Disruptor is a concurrent programming framework for exchanging and coordinating work as a continuous series of events.com.lmax.disruptor.dsl com.lmax.disruptor.util -
Classes in com.lmax.disruptor used by com.lmax.disruptor Class Description AbstractSequencer Base class for the various sequencer types (single/multi).AlertException Used to alertEventProcessors waiting at aSequenceBarrierof status changes.BatchStartAware Cursored Implementors of this interface must provide a single long value that represents their current cursor value.DataProvider EventFactory Called by theRingBufferto pre-populate all the events to fill the RingBuffer.EventHandler Callback interface to be implemented for processing events as they become available in theRingBufferEventPoller Experimental poll-based interface for the Disruptor.EventPoller.Handler EventPoller.PollState EventProcessor An EventProcessor needs to be an implementation of a runnable that will poll for events from theRingBufferusing the appropriate wait strategy.EventReleaser EventSequencer EventSink EventTranslator Implementations translate (write) data representations into events claimed from theRingBuffer.EventTranslatorOneArg Implementations translate another data representations into events claimed from theRingBufferEventTranslatorThreeArg Implementations translate another data representations into events claimed from theRingBufferEventTranslatorTwoArg Implementations translate another data representations into events claimed from theRingBufferEventTranslatorVararg Implementations translate another data representations into events claimed from theRingBufferExceptionHandler Callback handler for uncaught exceptions in the event processing cycle of theBatchEventProcessorInsufficientCapacityException Exception thrown when it is not possible to insert a value into the ring buffer without it wrapping the consuming sequences.LhsPadding LifecycleAware Implement this interface in yourEventHandlerto be notified when a thread for theBatchEventProcessorstarts and shuts down.NoOpEventProcessor.SequencerFollowingSequence Sequence that follows (by wrapping) another sequencePhasedBackoffWaitStrategy Phased wait strategy for waitingEventProcessors on a barrier.RhsPadding RingBuffer Ring based store of reusable entries containing the data representing an event being exchanged between event producer andEventProcessors.RingBufferFields RingBufferPad Sequence Concurrent sequence class used for tracking the progress of the ring buffer and event processors.SequenceBarrier Coordination barrier for tracking the cursor for publishers and sequence of dependentEventProcessors for processing a data structureSequenced SequenceGroup Sequencer Coordinates claiming sequences for access to a data structure while tracking dependentSequencesSingleProducerSequencerFields SingleProducerSequencerPad TimeoutException TimeoutHandler Value WaitStrategy Strategy employed for makingEventProcessors wait on a cursorSequence.WorkHandler Callback interface to be implemented for processing units of work as they become available in theRingBuffer.WorkProcessor AWorkProcessorwraps a singleWorkHandler, effectively consuming the sequence and ensuring appropriate barriers. -
Classes in com.lmax.disruptor used by com.lmax.disruptor.dsl Class Description EventFactory Called by theRingBufferto pre-populate all the events to fill the RingBuffer.EventHandler Callback interface to be implemented for processing events as they become available in theRingBufferEventProcessor An EventProcessor needs to be an implementation of a runnable that will poll for events from theRingBufferusing the appropriate wait strategy.EventTranslator Implementations translate (write) data representations into events claimed from theRingBuffer.EventTranslatorOneArg Implementations translate another data representations into events claimed from theRingBufferEventTranslatorThreeArg Implementations translate another data representations into events claimed from theRingBufferEventTranslatorTwoArg Implementations translate another data representations into events claimed from theRingBufferExceptionHandler Callback handler for uncaught exceptions in the event processing cycle of theBatchEventProcessorRingBuffer Ring based store of reusable entries containing the data representing an event being exchanged between event producer andEventProcessors.Sequence Concurrent sequence class used for tracking the progress of the ring buffer and event processors.SequenceBarrier Coordination barrier for tracking the cursor for publishers and sequence of dependentEventProcessors for processing a data structureTimeoutException WaitStrategy Strategy employed for makingEventProcessors wait on a cursorSequence.WorkerPool WorkerPool contains a pool ofWorkProcessors that will consume sequences so jobs can be farmed out across a pool of workers.WorkHandler 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.util Class Description EventProcessor An EventProcessor needs to be an implementation of a runnable that will poll for events from theRingBufferusing the appropriate wait strategy.Sequence Concurrent sequence class used for tracking the progress of the ring buffer and event processors.