Infront Data Manager Connect Client (.NET)

Usage notes

The API consists of four fundamental parts:

- Streaming Consumer Stores
- Routing Data Consumer Stores
- Retransmit Stores

In principle all streaming data connections are build as asynchronous connections. All messages from the transport layer are processed and backuped in separate threads and queues. This fact is very important for understanding the data processing.

Processing streamed data in customized code (Push Clients) can never block the transport layer. If your code can't process the incoming updates as they delivered to a Push Client the result will be, depending on the available memory, a OutOfMemoryException. This happens because all updates are internally stored in a queue.

Ensure that your code is fast enough to process all incoming updates!

## Streaming Consumer Stores

Streaming Consumer Stores are responsible for:

- Subscribing/Unsubscribing instruments, exchanges and news
- Management of inherent fault tolerance

Related pages:

- Subscribe Instruments
- Subscribe News Broadcast
- Subscribe Exchanges
- Request Recaps

## Routing Data Consumer Stores

Routing Data Consumer Stores are responsible for accessing master data and executing file downloads. They provide access to a wide range of functions in the Infront backend over the Data Manager Connect server infrastructure. In contrast to a Static Data Consumer Store a Routing Data Consumer Store provides a generic way to request any kind of static data without the need to enhance a core library of the Data Manager Connect.

You can use one instance of a Routing Data Consumer to execute all static data functions.

The documentation of all available routing data store interfaces and code samples can be dowloaded from https://www.vwd.com/ (closed user group).

Related pages:

- Download Files
- Historical Timeseries
- Index Composition
- ISIN Arbitrage List
- Get Symbol List for Exchanges
- Vwd Codes Helper

## Retransmit Stores

Retransmit Stores are responsible for requesting retransmits. Retransmits are Tick-By-Tick data as delivered in the original updates streams (Streaming Consumer Store), but for the past. You can request Tick-By-Tick data for the last 5 weekdays.

Related pages:

- Request Retransmits
- Process Status Messages

See also:

- Getting started
- Error Diagnostics
- Failover

Gevasys.DataCore
Definition: BinaryUpstreamClient.cs:5
Gevasys.DataCore.Configuration
Definition: ClassFactory.cs:17
Gevasys.DataCore.Consumer.Manager
Definition: ConsumerStore.cs:16
Gevasys.DataCore.Webservice
Definition: Webservice.Generated/Reference.cs:11
Gevasys.DataCore.StaticData
Definition: AsyncFileDownloader.cs:10
Gevasys.DataCore.Tools
Definition: FieldData.cs:4
Gevasys.DataCore.Client.PushClient.Update
abstract void Update(DataCore.Core.IConsumer source, ConsumerStateChangedEventArgs arg)
Abstract method that must be implemented in derived classes to recive status notifications for the un...
Example
Definition: DownloadFile.cs:5
Gevasys.DataCore.Client.PushClient.ProcessUpdates
abstract void ProcessUpdates(List< UpdateMessage > updates)
Gevasys.DataCore.Client
Definition: BinaryUpstreamClient.cs:5
Gevasys.DataCore.Core.Protocol
Definition: RequestStatusMessage.cs:8
Gevasys
Definition: BinaryUpstreamClient.cs:5
Gevasys.DataCore.Core
Definition: CompressionHelper.cs:7
Gevasys.DataCore.Consumer
Definition: ConsumerStore.cs:16
Examples
Definition: apiinitialize.cs:11
Gevasys.DataCore.StaticData.Http
Definition: AsyncFileDownloader.cs:10
Gevasys.DataCore.Tools.Protocol
Definition: ProtobufMessageHelper.cs:7

Copyright (C) 2021 Infront Financial Technology GmbH
Mainzer Landstrasse 178 – 190
60327 Frankfurt am Main
Infront Data Manager Connect V4.1