CourtHive/TMX makes use of IndexedDB to build a local database which includes (among other things) settings, players, rankings, tournaments, matches and points.
IndexedDB is part of all modern browsers, but its function can sometimes be restricted by particular browser settings, including Private Browsing.
CourtHive/TMX uses the Menu/Home Icon to indicate when there may be issues with the persistence of local data. If a possible issue is detected, the Menu/Home Icon turns Red. Data may still be saved, but it is not guaranteed, which means the User Agent may in some cases delete site-specific data.
See Tournament Information for instructions on how to push/pull copies of tournaments to/from the CourtHive Server and save copies of tournaments locally. See Local Player Database for instructions on how to maintain a local database of players to accommodate on-site sign-in of known players as well as historical match and ranking data for each known player.
The local database can be populated in two ways:
- Drag/Drop of JSON, XLSX, or CSV Files: See Importing/Exporting Local Data
- Fetching Data from the Cloud: See Uploading/Downloading Cloud Data
CourtHive/TMX uses Web Sockets to communicate with a CourtHive Cloud Server (CCS). The CCS can both manage a data store and access third party data stores, such as a database hosted on a server maintained by a national tennis federation, or even a Google Sheet.
When CourtHive/TMX has been configured with a key supplied by a third party organization it knows how to synchronize its local data with the remote data provided by the third party.