Inheritance diagram for CacheInvalidatee:
Public Member Functions | |
this (ICluster cluster, char[] channel, IMutableCache cache) | |
void | cancel () |
IMutableCache | getCache () |
Protected Member Functions | |
void | notify (IEvent event, IPayload payload) |
Private Member Functions | |
this (ICluster cluster, char[] channel) | |
IChannel | getChannel () |
ICluster | getCluster () |
long | getTime () |
IChannel | createChannel (char[] name) |
Static Private Member Functions | |
this () | |
Private Attributes | |
IMutableCache | cache |
ILogger | logger |
IConsumer | consumer |
Static Private Attributes | |
NullMessage | EmptyMessage |
Definition at line 61 of file CacheInvalidatee.d.
|
Construct a CacheInvalidatee upon the given cache, using the named channel. This channel should be a name that's common to both the receiver and the sender. Definition at line 75 of file CacheInvalidatee.d. References cache. |
|
Detach from the network. The CacheInvalidatee is disabled from this point forward. Definition at line 100 of file CacheInvalidatee.d. References IConsumer::cancel(), and consumer. |
|
Return the IMutableCache instance provided during construction Definition at line 111 of file CacheInvalidatee.d. References cache. |
|
Notification callback from the listener. We remove the indicated entry from our cache and destroy the payload immediately in case it belongs on a freelist. Reimplemented from IEventListener. Definition at line 124 of file CacheInvalidatee.d. References cache, IPayload::destroy(), IMutableCache::extract(), IEvent::getChannel(), IChannel::getName(), InvalidatorPayload::getText(), InvalidatorPayload::getTimeout(), ILogger::isEnabled(), ILevel::Level, logger, and ILogger::trace(). |
|
Definition at line 63 of file Client.d. References Client::EmptyMessage. |
|
Construct this client with the specified channel and cluster. The former specifies something akin to a 'topic', whilst the latter provides access to the underlying functional substrate (the QOS implementation). A good way to think about channels is to map them directly to a class name. That is, since you send and recieve classes on a channel, you might utilize the class name as the channel name (this.classinfo.name). Reimplemented in CacheInvalidator, NetworkAlert, NetworkCache, and NetworkQueue. Definition at line 80 of file Client.d. References Client::channel, and Client::cluster. |
|
Return the channel we're tuned to Definition at line 94 of file Client.d. References Client::channel. |
|
Return the cluster specified during construction Definition at line 105 of file Client.d. References Client::cluster. |
|
Return the number of milliseconds since Jan 1st 1970 |
|
Create a channel with the specified name. A channel represents something akin to a publush/subscribe topic, or a radio station. These are used to segregate cluster operations into a set of groups, where each group is represented by a channel. Channel names are whatever you want then to be; use of dot notation has proved useful in the past. In fact, a good way to think about channels is to map them directly to a class name. That is, since you typically send and recieve classes on a channel, you might utilize the class name as the channel (this.classinfo.name). Definition at line 136 of file Client.d. References Client::cluster, and ICluster::createChannel(). |
|
Definition at line 63 of file CacheInvalidatee.d. Referenced by getCache(), notify(), and this(). |
|
Definition at line 64 of file CacheInvalidatee.d. Referenced by notify(). |
|
Definition at line 65 of file CacheInvalidatee.d. Referenced by cancel(). |
|
Definition at line 61 of file Client.d. Referenced by Client::this(). |