Table of Contents

Eventing or polling

Unless the gRPC connection type is used (supported from DataMiner 10.3.0/10.3.2 onwards,) connections between a client application and a DMA as well as connections between two DMAs are established via a single user-defined TCP port over .NET Remoting.

DMAs can send notifications toward client applications by means of two different methods:

  • Eventing: Default method. The DMA will send server-initiated notifications to the client. As such, when a client application (e.g. DataMiner Cube) connects to a DMA, it will open a random port on the client to which the DMA will send its notifications. This method offers the best performance, but is not firewall-friendly.

    If .NET Remoting is used, the client will automatically fall back to polling if the callback port cannot be reached (e.g. if a firewall blocks the requests). If gRPC is used, the default HTTPS port is used, so no automatic fallback to polling is needed.

  • Polling: The DMA will not send server-initiated notifications to the client. Instead, the client application will continuously poll the DataMiner Agent for notifications. Use this method if there are firewalls in your network or if NAT is being used.


Within a DataMiner System, some connections can be configured to use eventing, while others can be configured to use polling.