Redbex Reference Manual

Zoom Window Out
Larger Text | Smaller Text
Hide Page Header
Show Expanding Text
Printable Version
Save Permalink URL

Navigation: Smart Client > Administration

Versioning

Over time the Smart Client will be deployed in different versions, new features might be added, bugs removed etc. To distinguish between different versions of the Smart Client each version has a unique version number. Version numbers consist of four components: major, minor, build, and revision e.g. 1.38.16312.16318. All components are integers greater than or equal to 0. The format of the version number is as follows:

The components are used by convention as follows:

•Major: A higher major version number indicates a major rewrite of a product or significant new functionality.

•Minor: If the major version number on two Smart Client versions are the same, but the minor version number is different, this indicates functionality enhancements.

•Build: A difference in build number indicates a new version with no significant new features implemented, but small improvements and bug fixes.

•Revision: A difference in revision number indicates a new version with small changes, mostly bug fixes.

Figure 1: The version of the Smart Client is shown on the Smart Client in the Backstage View

Application Server version compatibility

When the Smart Client connects to the Application Server it first gets the Application Server Version and checks if it supports that version. This is done by comparing the major and minor component of the Application Server version number to a compatibility version number that is hard coded within the Smart Client. If the Smart Client does not support that Application Server version you will not be able to connect.

Depending on your configuration (see also Smart Client common settings) of your Smart Client the Smart Client can automatically try do download a new version whenever it detects an incompatibility with the Application settings.

it will not connect but will try to download a version of the Smart Client that is compatible with the Application Server Version.

Example: If the Application Server compatibility number stored within the Smart Client is 2.3 the Smart client can connect to any Application Server whose version number has major component 2 and minor component 3.