Client types

The httpClient module provides two options for creating clients: a standalone HttpClient component and a multple-endpoint HttpClientNetwork component.
Figure 1.   Client types
Image

Standalone HttpClient

You may use this standalone component to make individual connections to single endpoints using any type of request (GET/POST/PUT) with several configurations, such as parameters, headers and message body. A user invocation or an input into the Send action slot triggers the HttpClient component’s Send action.

 
NOTE: You must enable the Standalone client type in the HttpClientService prior to use.
 

HttpClientNetwork

This component offers the same functionality as the standalone client, but allows several related endpoints to exist as child StringPoint components with configurable proxy extensions per request. Each request can have a different address or a different set of parameters, headers and message body. As the points are part of the standard Niagara driver model, the driver polls these string components according to its tuning policy.

Other benefits include:

  • Writable points with priority levels
  • The ability to add history, alarm ad other extensions
  • Manager views
  • Optional device ping to indicate service health