I have some questions about how Updater is implemented and how it works.
My understanding is as follows - please correct me if I am wrong:
a) There is client side component of Updater. This is an executable which is to be installed on machine which is to receive the update. This consists of a standard executable which can be included as part of the installation package. This executable is built by and provided by the AI team.
b) The client side component can (optionally) be invoked from my application.
c) There is a server side component of Updater which receives requests for updates and has the logic to determine if the request is valid and if there is an update available and if so will provide an MSI to the requesting client.
So, some questions:
1) Can my application which provides the interface to the client side component of the Updater, be part of the download that may result? If so then will the installer somehow shutdown my application before it begins the install process?
2) Who builds the server side component of the Updater? Do I do it or is it provided by AI?
3) If the answer to #2 is "AI" then what is the logic that it uses for licence validation and determining if an update is available?
4) If the answer to #2 is "I do it" then where can I find the definition of the interface to the client side component i.e. so that I can know what input to expect and what output that I should produce?
Thanks,
cats