Difference between revisions of "Melissa Releases:Best Practices"
Jump to navigation
Jump to search
(Created page with "{{ MelissaReleasesNav |IntroductionCollapse= }} {{CustomTOC}} ==Polling for Updates== The first concern is whether or not an update is necessary. Melissa releases updates for our products on a regular basis that varies from product to product. So, checking the current version against your own is an important step in minimizing unnecessary resource usage and downtime associated with updates. By polling the server at regular intervals, you can automatically monitor for a...") |
|||
| Line 2: | Line 2: | ||
|IntroductionCollapse= | |IntroductionCollapse= | ||
}} | }} | ||
{{CustomTOC}} | {{CustomTOC}} | ||
Latest revision as of 00:50, 15 March 2023
| Melissa Releases Navigation | |||||||
|---|---|---|---|---|---|---|---|
| |||||||
|
Polling for Updates
The first concern is whether or not an update is necessary. Melissa releases updates for our products on a regular basis that varies from product to product.
So, checking the current version against your own is an important step in minimizing unnecessary resource usage and downtime associated with updates. By polling the server at regular intervals, you can automatically monitor for and download updates as they become available.
There are a couple options:
- Compare the version number of the latest available release to the latest one that was downloaded. See the releases endpoints.
- This requires keeping track of the release number when downloading new releases; consider environment variables or a version tracking file.
- Compare the hash values of the latest available release file(s) to the hash values of the existing files. See the hash value endpoints.
- The hash values of local files should be compared to the hash values returned by the Hash Type endpoints to ensure the integrity of each download.
- By storing or calculating this hash value again, you can compare it to the hash values of the latest release for each file.