...
In ecflow 4. series, we used boost Serialisation for the client/server communication.
If we used Using the same boost version it meant that different version of ecflow 4.X.X releases had client/server that could be used interchangeably.
...
For the stats command in 4 series version , the sever server returns a struct for the statistics, the client then formats this.
...
Whenever the server checkpoints(i.e saves the definition state) , the full defs definition is written to disk.
The checkpoint uses ecFlow definition format, where writing to disk and reading it back into memory, can done faster the boost or even Json serialisation.
...
If any user requests the full defs definition, we can return cache cached string really fast.
Auto Sync
In the 4 series, whenever the GUI makes a change, it involves two calls to the server.
...
This reduces the latency for GUI and python clientsclients and improves responsiveness.