<< Click to Display Table of Contents >> Navigation:  Components > Communication > Multi-IO-IP > Transport type

TCP

By using the TCP protocol, you can only send data (TCP client). There must be a TCP server.

 

UDP

By using the UDP protocol, you can receive both data (UDP servers) and send data (UDP clients).

Note: When receiving UDP data, a filter must be defined.

 

HTTP

By using the HTTP protocol, you can send "HTTP-GET Web Requests" to a Web server, thereby executing specific commands or retrieving entire documents and parse through the use of the receive filters.

 

A number of filters exist to extract certain values ​​from arbitrarily formatted data structures. These filters can, for example, parse XML documents after retrieving an XML document from a Web server and extract a specific value. It can then be converted to an internal data type configured in the editor and passed to a data point output.

The individual setting options in the dialogs are explained below.

 

The configuration options for TCP / UDP differ from those for HTTP. Therefore, any inputs in the HTTP input list are not visible in the TCP / UDP and vice versa. If you change the transport type, you must confirm that the list is deleted.

 

TCP / UDP differs from HTTP in several points:

For HTTP, only string strings can be sent. On the other hand, binary data can also be sent using TCP / UDP.

In order to retrieve, evaluate and convert certain data into polar bear internal data types, HTTP offers the possibility to extract certain XML data from the response from the web server and then convert it and forward it to an output in the EisBaer network.

TCP / UDP, on the other hand, can control devices in the u.a. Also binary data are sent and corresponding answers are compared with parameterized positive or negative acknowledgments.