General compatibilty information

The original TBXDS (version 1.0 that is), ignored any version attribute, and passed the value to the corresponding response version attribute, without changing the actual data format, or even checking the validity of the version attribute.

TBXDS/3 will fail, however, when a version attribute is supplied that is not recognised; omitting the version attribute in the request message is also not permitted, since the TBXDS/3 engine will not be able to determine which version to return, and how to interpret your request. This means that the output data will not change its structure when the TBXDS engine is updated or changed in future releases.

If in a future release, the TBXDS engine will discontinue a certain compatibility mode, this will be communicated to the TBXDS customers. All future releases will be accompanied by a statement from Infront, that the clients' software should ideally be upgraded to support the latest version.

Note When a certain version's support is discontinued, you will receive the latest version's MetaData error message stating that the requested version is obsolete.

Also, the attributes user-name and user-key are available since version 2 (build 408), and can be used instead of the HTTP variables (USER and PWD); versions before 2.0 did not require user authentication, but even TBXDS/3 compatibility mode 1.1 requires this information, and thus it also accepts user-name and user-key.