...
ecFlowUI can observe and interact with many ecFlow servers at the same time. Server communication has the potential to be costly in terms of network usage and in waiting time, therefore ecFlowUI uses a separate execution thread for communicating with each server. This allows the user interface to remain responsive while communicating with busy servers. ecFlow servers can have a heavy load, so ecFlowUI employs some strategies to reduce server requests.
Each tab in ecFlowUI is linked to a specific set of servers; if you have multiple tree or table views in a tab, they will all by linked to the same set of servers.
| Anchor | ||||
|---|---|---|---|---|
|
To save screen space and to reduce load on the server, ecFlowUI allows you to select a subset of the available suites on a given server. Select the server node in the tree, go to the Info Panel and select Suite Filter. Enable the filter, then select just those suites of interest and click the Submit button. This informs the server that you only require updates for those suites, thus reducing network traffic and server load.
Refreshing and resetting a server
After initially loading a server's node tree, ecFlowUI will automatically refresh, or synchronise with, the server at regular intervals. This interval can be set globally for all servers in the Edit | Preferences | Server Options dialogue, or for each server individually by selecting the Server Settings tab in the Info Panel while a server's root node is selected. If a suite filter is enabled, the synchronisation process only considers those suites. There are three possible outcomes from the refresh:
- nothing has changed on the server since the last synchronisation
- minor changes have occurred, such as nodes changing their status - the changes are sent by the server and incorporated into ecFlowUI's tree
- major changes have occurred, such as nodes being added or removed - a complete new tree is sent by the server, causing a full reset of ecFlowUI's storage of the tree; this is a more costly operation
...