Version 4.1
The current release 4.1 of the "Infront Data Manager Connect" client now supports Transport Layer Security (TLS).
Please find below the description of the new features, functions and amendments included in our latest Release 4.1.
Security
With Release 4.1, we are introducing a DMC client/server software version that can deliver Transport Layer Security (TLS) encrypted streaming data.
The client API 4.1 is backward compatible with DMC server versions that do not use TLS encryption (version < 4.1).
The whole encryption process is encapsulated in the client library functionality, so no adjustment is needed on the customer side.
If you are interested in enabling and using the TLS encryption feature, please contact your Infront key account manager or our customer service. We will set up a 4.1 DMC server for you so that TLS is enabled and encrypted data is sent to the client API.
Your client API will discover the TLS encryption automatically.
- For more information, see "TLS encryption". This document describes further technical details, for example, about certificate pinning.
- The config parameters were enhanced due to these technical innovations. You can find the description of the config parameters included in the developer documentation in the client API delivery (CHM file), chapter "Configuration", beneath "Usage Notes" → "Getting Started".
Reminder:
In an earlier release, we have already renamed the configuration parameters to conform to the Infront naming conventions ("vwd" has been replaced by the product name "DMC"). There is no urgent need for action on the part of the customer because we have specified the configuration to be downward compatible. However, the "vwd" names in the configuration should be replaced with "DMC" names as soon as possible.
Troubleshooting
We have improved our exchange symbol list fetch procedure, which provides the instrument symbols available to our customers.
In case of a disturbance, the system will now provide at least the symbols from up to 3 days ago for a given trading venue instead instead of an empty symbol list as before.
Improve stability
The client API provides a so-called RequestRecaps function, which can be used to request master data for a specific list of instruments (in push mode).
We decided to limit this list to a maximum of 2000 symbols in order to avoid heavy load on our interfaces.
If you use this feature, please adjust your implementation accordingly. If the maximum number of symbols is exceeded, then the list is truncated accordingly.
Simply download the new version from the Closed User Group and replace the libraries of the previous versions.