UMPS
The University of Utah Seismograph Stations Message Passing System.
uRemoteCommand

Allows privileged users to interact with remotely running modules. More...

Collaboration diagram for uRemoteCommand:

Classes

class  UMPS::ProxyServices::Command::AvailableModulesRequest
 Requests the available modules that have been registered with the remote module monitoring service. More...
 
class  UMPS::ProxyServices::Command::AvailableModulesResponse
 Returns the available modules that have been registered with the remote module monitoring service. More...
 
class  UMPS::ProxyServices::Command::ModuleDetails
 Defines the module properties. More...
 
class  Proxy
 This is the intermediary that allows communication between a client and a backend service. More...
 
class  UMPS::ProxyServices::Command::ProxyOptions
 Defines the options for the command proxy. More...
 
class  UMPS::ProxyServices::Command::RegistrationRequest
 Allows servers to request becoming a registered modules. More...
 
class  UMPS::ProxyServices::Command::RegistrationResponse
 The response to a module registration response. More...
 
class  UMPS::ProxyServices::Command::Replier
 A replier mechanism for the server in the remote command service. More...
 
class  UMPS::ProxyServices::Command::ReplierOptions
 Defines the options for the thread managing remote activity to respond. More...
 
class  ReplierPRocess
 This process will respond to remote module interaction messages. More...
 
class  UMPS::ProxyServices::Command::Requestor
 This class allows the user to interact with programs running remotely i.e., - on a different machine. Nominally, you will only want this to be used by privileged users that you trust. More...
 
class  UMPS::ProxyServices::Command::RequestorOptions
 This sets the parameters for the utility that will allow users to interact with remote modules. More...
 

Detailed Description

Allows privileged users to interact with remotely running modules.

uRemoteCommand

This utility is for interacting with modules running on other machines. The idea is to allow a privileged user to interact with a daemon process on another computer. The catch here is that a remote module must be registered. This means handing over some autonamy to UMPS.