The deSide Updater is the core of the entire deSide Suite. This is the application that is responsible for downloading and processing all of the important data that the deSide Client and deSide Ticker display. You can see more detail about the general structure of the deSide Updater at this page.

However, even with its importance in the system, once installed the deSide Updater requires very little interaction from the user, and very little can actually be done with it directly. It simply sits quietly on the machine, silently downloading and updating data into your deSide Database.

Components

The deSide Updater consists of one component, the actual Update Engine, which is responsible for downloading, verifying and processing the data files for the various data sets stored and updated on our multiple data servers. This component is represented by the global-roam Data Service tab. During normal operations, the contents of this tab will look something like the following.

Each of the root trees in the picture above represent a specific file type being downloaded, and when you expand the tree, you see the file type name again, with a server name appended to the end. These sub-trees represent the collection of files of this type that the updater is downloading from each server. Going down further, you can see the exact list of file names that the application is downloading from that specific server, along with a status entry at the end of the line. You can see this a bit more clearly in the following image.

There is another component in the deSide Updater, but it is merely there for legacy support. It is the component represented by the global-roam Data Management tab. This tab doesnt do much anymore, and you dont need to worry about it.

Operating Modes

The deSide Updater can run in 2 modes. It can run as an Application, or as a Service. We've provided these two options for those who want a choice as to how their Updater will run on their computer (i.e. to allow you a little bit more control). These two options are outlined below.

• Application - When running as an application, the deSide Updater has all of its usual functionality. However, if your machine restarts, or you do not want to remain logged in under the current user, the application version of the deSide Updater will longer run. Running the deSide Updater in Application mode makes it easier to set up however, and we suggest your first run of the Updater be in Application mode.
• Service - When running as a Service, the deSide Updater will run any time the computer is on. Even when you are logged out (as long as the machine is on), the deSide Updater will be running. However, when running as a Service, the deSide Updater is harder to configure, so as suggested above, your first run of the Updater should be in Application mode.

Switching between the two modes is a fairly simple process, under the File menu, you will find entries for Application and Service, and under each of these you will be able to Stop and Start the mode at will (you cannot run both at the same time, and the application will prevent you from doing this by greying out the appropriate options).