Uses of Package
com.lmax.disruptor

Packages that use com.lmax.disruptor

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

AbstractMultithreadedClaimStrategy

AlertException
Used to alert EventProcessors waiting at a SequenceBarrier of status changes.

BatchDescriptor
Used to record the batch of sequences claimed via a Sequencer.

ClaimStrategy
Strategy contract for claiming the sequence of events in the Sequencer by event publishers.

EventFactory
Called by the RingBuffer to pre-populate all the events to fill the RingBuffer.

EventHandler
Callback interface to be implemented for processing events as they become available in the RingBuffer

EventProcessor
EventProcessors waitFor events to become available for consumption from the RingBuffer An EventProcessor will be associated with a Thread for execution.

EventTranslator
Implementations translate another data representations into events claimed from the RingBuffer

ExceptionHandler
Callback handler for uncaught exceptions in the event processing cycle of the BatchEventProcessor

InsufficientCapacityException

LifecycleAware
Implement this interface to be notified when a thread for the BatchEventProcessor starts and shuts down.

RingBuffer
Ring based store of reusable entries containing the data representing an event being exchanged between event publisher and EventProcessors.

Sequence

SequenceBarrier
Coordination barrier for tracking the cursor for publishers and sequence of dependent EventProcessors for processing a data structure

Sequencer
Coordinator for claiming sequences for access to a data structure while tracking dependent Sequences

TimeoutException
Used to signal that an operation has timed out and been aborted.

WaitStrategy
Strategy employed for making EventProcessors wait on a cursor Sequence.

WorkHandler
Callback interface to be implemented for processing units of work as they become available in the RingBuffer

Classes in com.lmax.disruptor used by com.lmax.disruptor.dsl

ClaimStrategy
Strategy contract for claiming the sequence of events in the Sequencer by event publishers.

EventFactory
Called by the RingBuffer to pre-populate all the events to fill the RingBuffer.

EventHandler
Callback interface to be implemented for processing events as they become available in the RingBuffer

EventProcessor
EventProcessors waitFor events to become available for consumption from the RingBuffer An EventProcessor will be associated with a Thread for execution.

EventTranslator
Implementations translate another data representations into events claimed from the RingBuffer

ExceptionHandler
Callback handler for uncaught exceptions in the event processing cycle of the BatchEventProcessor

RingBuffer
Ring based store of reusable entries containing the data representing an event being exchanged between event publisher and EventProcessors.

SequenceBarrier
Coordination barrier for tracking the cursor for publishers and sequence of dependent EventProcessors for processing a data structure

WaitStrategy
Strategy employed for making EventProcessors wait on a cursor Sequence.

Classes in com.lmax.disruptor used by com.lmax.disruptor.util

EventProcessor
EventProcessors waitFor events to become available for consumption from the RingBuffer An EventProcessor will be associated with a Thread for execution.

Sequence