Inheritance diagram for NetworkQueue:
Public Member Functions | |
this (ICluster cluster, char[] channel) | |
IConsumer | createConsumer (IEventListener listener) |
void | put (IPayload payload) |
IPayload | get () |
Private Member Functions | |
IChannel | getChannel () |
ICluster | getCluster () |
long | getTime () |
IChannel | createChannel (char[] name) |
Static Private Member Functions | |
this () | |
Static Private Attributes | |
NullMessage | EmptyMessage |
Definition at line 49 of file NetworkQueue.d.
|
Construct a NetworkQueue gateway on the provided QOS cluster for the specified channel. Each subsequent queue operation will take place over the given channel. Reimplemented from Client. Definition at line 59 of file NetworkQueue.d. |
|
Create a listener for this channel. Listeners are invoked when new content is placed into a corresponding queue. Definition at line 71 of file NetworkQueue.d. References ICluster::createConsumer(). Referenced by testClusterMessage(), and testClusterQueue(). |
|
Add an IPayload entry to the corresponding queue. This will throw a ClusterFullException if there is no space left in the clustered queue. Definition at line 84 of file NetworkQueue.d. References ICluster::putQueue(). Referenced by testClusterQueue(). |
|
Query the cluster for queued entries on our corresponding channel. Returns, and removes, a matching entry from the cluster. This is the synchronous (polling) approach; you should use createConsumer() instead for asynchronous style notification instead. Definition at line 99 of file NetworkQueue.d. References ICluster::getQueue(). |
|
Definition at line 63 of file Client.d. References Client::EmptyMessage. |
|
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 61 of file Client.d. Referenced by Client::this(). |