▼Messages | |
Abstract Message Base Class | The class that allows messages to be created, transmitted, and reconstituted by another machine |
Message Formats | Some message formats provided by UMPS |
▼Messaging Patterns | |
Context | A context is like a thread used by ZeroMQ to send and receive messages |
Introduction | Messaging patterns enabled by UMPS |
▼Publisher-Subscriber Patterns | |
Publisher-Subscriber | The publisher-subscriber pattern is the simplest communication mechanism. It is included for pedagogical purposes only. Here, multiple consumers receive messages from one producer |
Extended Publisher-Subscriber | A fully asynchronous publish-subscribe mechanism whereby a forwarder (proxy) relays messages from multiple publishers to multiple subscribers |
▼Request-Reply Patterns | |
Router-Dealer | The router-dealer combination allows for asynchronous clients interacting with asynchronous servers |
Request-Router | The request-router combination allows for an asynchronous server that can be utilized by multiple clients.
|
▼Authentication | |
Introduction | Introduction to the authentication section |
Security Levels | Defines the various supported security levels in UMPS |
User Privileges | Defines the minimum required user-privileges to access various messaging relays |
▼ZeroMQ Authentication Protocol | Options for the interacting with the ZeroMQ authentication protocol |
Cerficates | The class defining how credentials are stored and how they map to various security levels |
▼Authentication Service | Authentication services are run by the uOperator. Whenever a connection is formed, the ZeroMQ will call this service which, in turn, calls the authenticator to validate the connection |
Authenticator | The authenticator implements the requisite business logic to validate a connection. It is called by the service |
▼Utilities | Programs for interacting adding/updating/removing users from the users table and generating key-pairs |
▼User Table | On the server, all user credentials are stored in a single database. This program facilitates interaction with that database |
User | This defines a user - who is someone who can be added to the database |
▼Logging | |
Introduction | Introduction to the logging section |
Logging Base Class | For those wishing to make their own loggers |
Provided Loggers | Useful loggers that ship with UMPS |
▼Modules | |
Module Base Class | This is a container for the processes that constitute a program |
Process Base Class | Processes are independent components of a program - e.g., heartbeating |
▼Applications | |
uOperator | The critical message relay hub in the hub and spoke architecture |
uCommand | Allows users to interact with locally running modules |
uRemoteCommand | Allows privileged users to interact with remotely running modules |