The DDserver is the server on the same host as the DD pool, which talks to a remote DD client.
The DDserver is the server on the same host as the DD pool, which talks to a remote DD client. There is one DDserver per client.
The server is forked off by the DDdemon upon request of a remote client and connects itself through a socket the client. It receives the commands from the socket, interprets and executes them and returns the result to the client.
Commands in form of the class ddnCmd are exchanged between server and client. The typical mode of operation is that the server waits on the socket to received an instance of the class ddnCmd and reads its command code. Then depending on the command code it reads additional parameter from the socket, before calling the corresponding DD routines. Note that this might also take some time, especially when the server wants to retrieve a rare event from the pool which may involving sleeping on a semaphore. Finally the server returns all parameters back to the client.
We follow the philosophy of the network utilities of the package OTOOLS.
- otnetObject: abstract interface for data exchange over sockets (package OTOOLS)
- otnetDemon: abstract interface of a TCP/IP demon (package OTOOLS)
- ddnCmd: Class that encapsulates a DD command, inherits from otnetObject
- ddnFifoEntry: wrapper class around the FifoEntry class
- ddSpecs: subtype of otnetObject, specifies all parameters of the DD system
- DDserver: This class: implements the actual server
The server is invokes after fork by the DD demon by calling the static member function startup, which in turn creates the DDserver object.
Alphabetic index HTML hierarchy of classes or Java