next up previous contents
Next: 3. Status Server System Up: Status Server Detailed Design Previous: 1. Introduction   Contents

Subsections

2. Development and Execution Environment

Both the Status Server and Client API library will be developed using the C language and conform to the established CFHT coding standard. The software will be compiled for the three major UNIX architectures in use at CFHT; HP-UX, Sun Solaris, and Linux. The Client API library will be available on the three previously mentioned architectures.

2.1 Hardware

The amount of processing power required to run the Status Server is largely dependent on the load placed upon it by its client connections. Based on the previously defined requirement that clients not update data at frequencies greater than 1 Hz, a moderately configured system should be more than sufficient to run the Status Server. Benchmarking must be performed following implementation to determine what the typical memory and CPU utilization for the Status Server will be.

The machine running the Status Server must have a 100Mbps Ethernet connection and be accessible by other machines on the CFHT network.

2.2 Software

Clients wishing to use the Client C-API must be running either HP-UX, Sun Solaris, VxWorks, or Linux. The C-API library will be compiled and linked as a static library target.


next up previous contents
Next: 3. Status Server System Up: Status Server Detailed Design Previous: 1. Introduction   Contents
Tom Vermeulen
2011-01-26