When an application is completely in the clients permanent storage cache and therefore can be executed offline, how can the client be notified about a new version available?
A14. The responsibility of the Code Server, starting with the Mini-CS on the client, is to check with its immediate superior if there is a change in status of the code file in question. It will make the same request to the Code Server it made before. If the answer it gets is different (eg checksum has changed) then it knows to download the new version. And the Code Server will check with its immediate superior in the same way. Of course when a change is made at the source level (way out there at the Guru’s computer to use our earlier example), there are two ways such a change can be forced all the way to the user a. The Code Server periodically polls its superior for all “known” modules every so many hours/days/invocations. b. The Guru (software maintainer) can send down a flag to the Code Server network to specifically force the clearing of the “ok” flag for that module. Of course even then the download doesn’t actually take place until there is a request for the object. All this is t
Related Questions
- When an application is completely in the clients permanent storage cache and therefore can be executed offline, how can the client be notified about a new version available?
- Does the BRMS Application Client use save files to save objects and do I need 1 gigabyte of system storage in order to save a 1 gigabyte database to an TSM server?
- What is meant by online versus offline restores? How is this affected by the client software’s local storage feature?
