Search Results for "tcp api"

...Supported embedded architectures: ESP32, NRF52, STM32, NXP, and more. Built-in protocols: plain TCP/UDP, HTTP, MQTT, Websocket. SSL/TLS support: mbedTLS, OpenSSL or custom (via API). Used to solve a wide range of business needs, like implementing Web UI interface on devices, RESTful API services, telemetry data exchange, remote control for a product, remote software updates, remote monitoring, and others.

Like libevent, libev, and libuv, libhv provides event loop with non-blocking IO and timer, but simpler api and richer protocols. Cross-platform (Linux, Windows, MacOS, BSD, Solaris, Android, iOS) High-performance EventLoop (IO, timer, idle, custom) TCP/UDP client/server/proxy. TCP supports heartbeat, reconnect, upstream, MultiThread-safe write and close, etc. Built-in common unpacking modes (FixedLength, Delimiter, LengthField) RUDP support: WITH_KCP.

GWS is a high-performance WebSocket library for Go that provides both server and client capabilities. It is designed for high-concurrency use cases such as API gateways, chat systems, reverse proxies, online games, real-time streaming, and push or subscription services. The library exposes a minimal event-driven API, allowing developers to build WebSocket applications with relatively little code. It supports standard TCP usage as well as WebSocket operation over KCP and Unix domain sockets. ...

...In addition to detailed documentation and examples, the API is unified in style and the same types and API used for HTTP requests is used for JSON and Mustache rendering - so there's less to learn. facil.io should work on Linux / BSD / macOS (and possibly CYGWIN) and is continuously tested on both Linux and macOS.

N2O is an embeddable message protocol loop library for WebSocket, HTTP, MQTT and TCP servers. It provides basic features, such as process management, virtual nodes ring for request processing, sessions, frame encoding, and unified API for external mq and caching services.

The WebSocketListener class provides simple methods that listen for and accept incoming WebSocket connection requests asynchronously. It is a lightweight listener with an API very similar to the System.Net.TcpListener class. It does not use the Microsoft's System.Net.WebSockets namespace. WebSocketListener has been designed to provide WebSocket connectivity to other applications, in the same way that System.Net.TcpListener provides TCP connectivity. It is not a communication framework on its own and it does not provide any kind of publisher/subscriber pattern or reliable messaging beyond TCP.