So-called REST (Representational State Transfer) APIs are frequently offered by web servers in IoT communication in order to channel certain communication processes via a uniform and stateless interface. Although REST is basically independent of the transport system, the Internet of Things mainly uses the HTTP/HTTPS protocol established in web communication as, among other things, it enables better compatibility with firewalls. There are many different application scenarios for connecting an HTTP/REST interface from within the controller, ranging from the simple determination of weather data through to complex communication processes.
Ordering information | |
---|
TF6760-0v20 | TC3 IoT HTTPS/REST, platform 20 (Economy) |
TF6760-0v30 | TC3 IoT HTTPS/REST, platform 30 (Economy Plus) |
TF6760-0v40 | TC3 IoT HTTPS/REST, platform 40 (Performance) |
TF6760-0v50 | TC3 IoT HTTPS/REST, platform 50 (Performance Plus) |
TF6760-0v60 | TC3 IoT HTTPS/REST, platform 60 (Mid Performance) |
TF6760-0v70 | TC3 IoT HTTPS/REST, platform 70 (High Performance) |
TF6760-0v80 | TC3 IoT HTTPS/REST, platform 80 (Very High Performance) |
TF6760-0v81 | TC3 IoT HTTPS/REST, platform 81 (Many-core 5…8 Cores) |
TF6760-0v82 | TC3 IoT HTTPS/REST, platform 82 (Many-core 9…16 Cores) |
TF6760-0v83 | TC3 IoT HTTPS/REST, platform 83 (Many-core 17…32 Cores) |
TF6760-0v84 | TC3 IoT HTTPS/REST, platform 84 (Many-core 33…64 Cores) |
TF6760-0v90 | TC3 IoT HTTPS/REST, platform 90 (Other) |
TF6760-0v91 | TC3 IoT HTTPS/REST, platform 91 (Other 5…8 Cores) |
TF6760-0v92 | TC3 IoT HTTPS/REST, platform 92 (Other 9…16 Cores) |
TF6760-0v93 | TC3 IoT HTTPS/REST, platform 93 (Other 17…32 Cores) |
TF6760-094 | TC3 IoT HTTPS/REST, platform 94 (Other 33…64 Cores) |