TimeBase supports client-server communication via TCP, IPC, UDP and/or HTTP protocols.
TimeBase supports TCP protocol for wide area networks. Enabled by default for local and remote connections. TCP protocol is a good choice in case you are not targeting extra-low latencies in open networks .
When a TimeBase client connects to the server over TCP, it automatically performs a connection speed test by measuring the latency of a round-trip. TimeBase is able to detect whether the connection is over a LAN or a WAN/Internet. For wide area networks, TimeBase will compress non-live data before transmitting it in either direction in case round-trip latency exceeds 10ms.
See Architecture to learn more about system components and ecosystem.
Low latency data streaming protocol. Limited number of active clients due to the nature of the IPC protocol. IPC protocol is a good choice in case you are targeting extra-low latencies in a closed system with a defined and limited number of subscribers.
TimeBase supports HTTP/HTTPS protocol for REST/Websocket communication used by TimeBase Admin and Web Gateway. TimeBase Server listens to all (HTTP/HTTPS) connections on a single port and automatically upgrades the connection to SSL in case it is requested by the client.