RWTPCValBufferBaseGuarded<Type,GuardAndPriorityDecorator> RWTPCValBufferBaseGuardedPrioritized<Type,GuardAndPriorityDecorator>
#include <rw/itc/RWTPCValBufferBaseGuardedPrioritized.h>
RWTPCValBufferBaseGuardedPrioritized<...> is the base class for the family of classes that provide buffered producer-consumer synchronization semantics exchanging guarded and prioritized values between cooperating threads.
In the producer-consumer synchronization model, reader threads (consumers) are blocked while a buffer is empty, and writer threads (producers) are blocked while a buffer is full. A buffer is considered full when the number of unread entries equals or exceeds some user-specified maximum capacity.
The write operations provided by this class and its subclasses bind additional data items to each value prior to storing that value in an internal buffer. These additional data items, or decorations, include a guard functor instance and a priority value. The guard functor is used during read operations to determine whether the associated value is currently eligible for retrieval from the buffer. The priority value is used during write operations to determine a value's insertion point within the buffer, such that the set of unread values will be retrieved in priority order when eventually read from the buffer. The template parameter GuardAndPriorityDecorator identifies the class that is used to encapsulate the data value, guard functor, and priority value as a single object for storage in the internal buffer. The decorator class used by subclasses to instantiate this class is intended for the internal use of the library, and is not documented as part of the public interface.
virtual ~RWTPCValBufferBaseGuardedPrioritized();
Virtual destructor.
The following superclass functions have been redeclared or redefined to allow them to be overloaded within in this class:
RWBoolean tryWrite(const Type& value);
void write(const Type& value);
RWWaitStatus write(const Type& value,
unsigned long milliseconds);
These functions provide the same capabilities and behavior as their counter-parts in this class, except that these functions attach an empty guard functor instance and a priority value of zero to each value.
RWBoolean tryWrite(const Type& value,
const RWTFunctorR0<RWBoolean>& guard);
void write(const Type& value,
const RWTFunctorR0<RWBoolean>& guard);
RWWaitStatus write(const Type& value,
const RWTFunctorR0<RWBoolean>& guard,
unsigned long milliseconds);
These functions provide the same capabilities and behavior as their counter-parts in this class, except that these functions attach a priority value of zero to each value.
RWBoolean tryWrite(long priority, const Type& value);
void write(long priority, const Type& value);
RWWaitStatus write(long priority, const Type& value,
unsigned long milliseconds);
These functions provide the same capabilities and behavior as their counter-parts in this class, except that these functions attach an empty guard functor instance to each value.
RWBoolean
tryWrite(long priority, const Type& value,
const RWTFunctorR0<RWBoolean>& guard);
Inserts a value with the specified priority into the buffer at a position determined by the implementation supplied in derived classes, but only if the value may be written immediately; in other words, only if there is sufficient free capacity.
If the buffer is open and has sufficient capacity to hold another value, this function inserts the value, and returns a value of TRUE to indicate that the write succeeded. If the buffer is open and full, this function immediately returns a value of FALSE to indicate that the write was unsuccessful. If the buffer is closed, this function immediately returns by throwing an RWTHRClosedException.
Calling this function on a full buffer may result in the invocation of the on-full callback functor, if a valid one was registered. The on-full callback functor is guaranteed to execute only within a writer thread. Calling this function on a full buffer will result in the invocation of an on-full callback functor under either of these scenarios:
The calling thread is waiting on an full buffer when an on-full callback is registered.
The calling thread is the first to attempt writing to a full buffer in which an on-full callback was previously registered.
Repeated attempts to write to a full buffer will not result in repeated invocations of the callback functor. Once the full buffer is read from, however, it resets the callback trigger; should the buffer again become full, the first thread to attempt to write will cause another invocation of the on-full callback.
While this function guarantees not to block the caller if the buffer is full, it cannot prevent the on-full callback functor, if executed, from indirectly blocking the caller.
This function takes three parameters:
The parameter priority is a long that is used to determine the insertion point of the value with the buffer. A value with a greater priority value is positioned to be read before a value of lower priority. Values of equal priority are positioned as determined by the implementation supplied in derived classes.
The parameter value is a const reference to an instance of the type used to instantiate this template class.
The parameter guard is a reference to an RWTFunctorR0<RWBoolean> functor instance that will be invoked during read and peek operations to determine whether the associated value is currently eligible for reading. An empty functor handle indicates that the entry is always eligible for reading. The functor must not attempt to access the buffer instance as such access results in deadlock.
void
write(long priority, const Type& value,
const RWTFunctorR0<RWBoolean>& guard);
Inserts a value with the specified priority into the buffer at a position determined by the implementation supplied in derived classes.
If the buffer is open and has sufficient capacity to hold another value, this function inserts the value. If the buffer is open and full, this function blocks the calling thread until the buffer is no longer full (because another thread or threads have read values or have changed the maximum capacity), or until the buffer is closed.
If the buffer is closed while the calling thread is blocked and waiting within this function for room to write, the calling thread is unblocked and the function returns by throwing an RWTHRClosedException. If the buffer is already closed when this function is called, the function immediately returns by throwing an RWTHRClosedException.
Calling this function on an full buffer may result in the invocation of the on-full callback functor, if a valid one was registered. The on-full callback functor is guaranteed to execute only within a writer thread. Calling this function on a full buffer will result in the invocation of an on-full callback functor under either of these scenarios:
The calling thread is waiting on an full buffer when an on-full callback is registered.
The calling thread is the first to attempt writing to a full buffer in which an on-full callback was previously registered.
Repeated attempts to write to a full buffer will not result in repeated invocations of the callback functor. Once the full buffer is read from, however, it resets the callback trigger; should the buffer again become full, the first thread to attempt to write will cause another invocation of the on-full callback.
This function takes three parameters.
The parameter priority is a long that is used to determine the insertion point of the value with the buffer. A value with a greater priority value is positioned to be read before a value of lower priority. Values of equal priority are positioned as determined by the implementation supplied in derived classes.
The parameter value is a const reference to an instance of the type used to instantiate this template class.
The parameter guard is a reference to an RWTFunctorR0<RWBoolean> functor instance that will be invoked during read and peek operations to determine whether the associated value is currently eligible for reading. An empty functor handle indicates that the entry is always eligible for reading. The functor must not attempt to access the buffer instance as such access results in deadlock.
RWWaitStatus
write(long priority, const Type& value,
const RWTFunctorR0<RWBoolean>& guard,
unsigned long milliseconds);
Inserts a value with the specified priority into the buffer at a position determined by the implementation supplied in derived classes.
If the buffer is open and has sufficient capacity to hold another value, this function inserts the value and returns RW_THR_COMPLETED to indicate that the write succeeded. If the buffer is open and full, this function blocks the calling thread until the buffer is no longer full (because another thread or threads have read values or have changed the maximum capacity), or until the buffer is closed, or until the specified amount of time passes. If sufficient space does not become available within the specified amount of time, the function returns a value of RW_THR_TIMEOUT.
If the buffer is closed while the calling thread is blocked and waiting within this function for room to write, the calling thread is unblocked and the function returns by throwing an RWTHRClosedException. If the buffer is already closed when this function is called, the function immediately returns by throwing an RWTHRClosedException.
Calling this function on a full buffer may result in the invocation of the on-full callback functor, if a valid one was registered. The on-full callback functor is guaranteed to execute only within a writer thread. Calling this function on a full buffer will result in the invocation of an on-full callback functor under either of these scenarios:
The calling thread is waiting on an full buffer when an on-full callback is registered.
The calling thread is the first to attempt writing to a full buffer in which an on-full callback was previously registered.
Repeated attempts to write to a full buffer will not result in repeated invocations of the callback functor. Once the full buffer is read from, however, it resets the callback trigger; should the buffer again become full, the first thread to attempt to write will cause another invocation of the on-full callback.
While this function guarantees to wait, if necessary, for a period of time equal to or greater than the specified number of milliseconds, it cannot guarantee that the thread is actually scheduled for execution at the end of the timeout period. It cannot prevent the on-full callback functor from indirectly blocking the caller for an indefinite period of time.
This function takes four parameters:
The parameter priority is a long that is used to determine the insertion point of the value with the buffer. A value with a greater priority value is positioned to be read before a value of lower priority. Values of equal priority are positioned as determined by the implementation supplied in derived classes.
The parameter value is a const reference to an instance of the type used to instantiate this template class.
The parameter guard is a reference to an RWTFunctorR0<RWBoolean> functor instance that will be invoked during read and peek operations to determine whether the associated value is currently eligible for reading. An empty functor handle indicates that the entry is always eligible for reading. The functor must not attempt to access the buffer instance, since such access results in deadlock.
The parameter milliseconds is an unsigned long value that specifies the maximum number of milliseconds to wait for the operation to complete.
RWTPCValBufferBaseGuarded<Type,GuardDecorator>, RWTPCValBufferBasePrioritized<Type,PriorityDecorator>, RWTPCValQueueGuardedPrioritized<Type>, RWTPCValStackGuardedPrioritized<Type>
©Copyright 2000, Rogue Wave Software, Inc.
Contact Rogue Wave about documentation or support issues.