Details
-
Type:
Story
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: ts_auxiliary_telescope, ts_main_telescope
-
Labels:
-
Story Points:1
-
Epic Link:
-
Sprint:TSSW Sprint - Jan 03 - Jan 17
-
Team:Telescope and Site
-
Urgent?:No
Description
Please simplify the ESS RPi server's TCP/IP API to something like the following:
- The server starts writing data after a client connects and issues the configure command.
- The server stops writing data when a client disconnects.
Thus the server would support just one command. Two subtleties:
- The server should reject additional configure commands after the first one.
- A new client should always have to send the configure command in order to receive data. The server should not remember configuration from an earlier client.
Please also consider encoding the sensor name, timestamp, reply code, and sensor data fields as 4 separately named entities in published telemetry data, rather than as one heterogenous list of 4+ values. That would make the data and client code clearer.