The request-router combination allows for an asynchronous server that can be utilized by multiple clients.
More...
Classes | |
class | UMPS::Messaging::RequestRouter::Request |
A ZeroMQ request for use in the request-router combination. More... | |
class | UMPS::Messaging::RequestRouter::RequestOptions |
Defines the request socket options. More... | |
class | UMPS::Messaging::RequestRouter::Router |
A ZeroMQ router for use in the request-router combination. More... | |
class | UMPS::Messaging::RequestRouter::RouterOptions |
Defines the router socket options. A router works like a service. After binding to the endpoint, the service will run in a thread according to the following pseudo-code while (true) { Wait for message on the end point until specified time out if (Message Received) { Process message with callback Return response to sender. } if (Termination Requested) { Exit while loop. } }. More... | |
The request-router combination allows for an asynchronous server that can be utilized by multiple clients.
Those who are reading closely may wonder how UMPS provides for remote interaction with distributed modules. The answer is a router-router combination. This (difficult to implement) pattern allows for point-to-point communication over a network. At the moment, this pattern is not exposed in UMPS simply because for most applications it is not useful.