preferences:synchronisation

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
preferences:synchronisation [2023/09/02 00:52] – [16.07. Synchronisation preferences] Mark Gloverpreferences:synchronisation [2023/12/04 02:32] (current) – [The preferences] Kahn Wynyard
Line 26: Line 26:
     * **Sync time interval:** the number of minutes between attempts to synchronise with the primary server. Setting this to 0 pauses sync. Editable without clicking on the **Click to unlock** button but only if sync is enabled on this site (i.e. if **Sync ID** is greater than 0).     * **Sync time interval:** the number of minutes between attempts to synchronise with the primary server. Setting this to 0 pauses sync. Editable without clicking on the **Click to unlock** button but only if sync is enabled on this site (i.e. if **Sync ID** is greater than 0).
     * **Sync request size:** the number of requests to lump together when communicating with the primary server. If the internet connection is stable it is more efficient to have a larger number here. If the connection is less stable then it is better to have a smaller number.     * **Sync request size:** the number of requests to lump together when communicating with the primary server. If the internet connection is stable it is more efficient to have a larger number here. If the connection is less stable then it is better to have a smaller number.
-  * **Use js node HTTP client checkbox:** checking this causes mSupply to use a Node.js HTTP client instead of its built-in webserver to communicate with the primary server. This is advantageous in some situations. This option will be enabled if synchronisation is being used on this site. It is the one setting that can be changed without entering the authorisation code mentioned above. +  * **Use js node HTTP client checkbox:** This preference is not recommended and will be disabled in future versions of mSupply (v7.11 and above). Node JS was used in special circumstances where 4D HTTP handlers were not working well on cellular connections for certain regions. This has been improved and Node JS is no longer needed.
   * **Check connection button:** click on this to check the connection to the primary server. The button is available even if the settings have not been unlocked and will send a test request to the primary server (but only if sync is enabled on this site i.e. if **Sync ID** is greater than 0). The result of the request will be displayed in a message and will tell you whether this site can reach the primary server.   * **Check connection button:** click on this to check the connection to the primary server. The button is available even if the settings have not been unlocked and will send a test request to the primary server (but only if sync is enabled on this site i.e. if **Sync ID** is greater than 0). The result of the request will be displayed in a message and will tell you whether this site can reach the primary server.
  
  • Last modified: 2023/09/02 00:52
  • by Mark Glover