Summer.Batch.Infrastructure.Repeat.Support Namespace Reference
Classes | |
interface | IRepeatInternalState |
Internal interface for extensions of RepeatTemplate. More... | |
interface | IResultHolder |
Interface for result holder. More... | |
interface | IResultQueue |
Abstraction for queue of IResultHolder objects. Acts a bit like a BlockingQueue with the ability to count the number of items it expects to ever hold. When clients schedule an item to be added they call Expect()}, and then collect the result later with Take(). Result providers in another thread call Put(Object) to notify the expecting client of a new result. More... | |
class | RepeatInternalStateSupport |
Internal state support for Repeat. Mainly used to store encountered exceptions. More... | |
class | RepeatSynchronizationManager |
Global variable support for repeat clients. Normally it is not necessary for clients to be aware of the surrounding environment because a IRepeatCallback can always use the context it is passed by the enclosing IRepeatOperations. But occasionally it might be helpful to have lower level access to the ongoing IRepeatContext so we provide a global accessor here. The mutator methods (Clear() and Register(IRepeatContext) should not be used except internally by IRepeatOperations implementations. More... | |
class | RepeatTemplate |
Simple implementation and base class for batch templates implementing RepeatOperations. Provides a framework including interceptors and policies. Subclasses just need to provide a method that gets the next result and one that waits for all the results to be returned from concurrent processes or threads. More... | |
class | ResultHolderResultQueue |
An implementation of the Summer.Batch.Infrastructure.Repeat.Support.IResultQueue<TB> that throttles the number of expected results, limiting it to a maximum at any given time. More... | |
class | TaskExecutorRepeatTemplate |
Support for RepeatOperations, including interceptors (used to modify or monitor the behavior at run time). Thread-safe class, provided that its collaborators are thread-safe as well. More... | |