Search Results for "java client server tcp"

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. SSL/TLS support: (via WITH_OPENSSL or WITH_GNUTLS or WITH_MBEDTLS) HTTP client/server (support https http1/x http2 grpc). HTTP supports static service, indexof service, proxy service, sync/async API handler. ...

frp stands for exactly what it is: a fast reverse proxy. It helps you expose a local server behind a NAT or firewall to the Internet. It is currently under development, but already supports TCP and UDP, as well as HTTP and HTTPS protocols where requests can be forwarded to internal services by domain name. It also has a P2P connect mode and many other nifty features. These include configuration files, environment variables, a dashboard that shows you frp's status and proxies' statistics...

paqet is a bidirectional packet-level proxy that transports traffic over raw packets instead of relying on the host operating system’s normal TCP/IP stack. It forwards traffic between a local client and a remote server using KCP as the reliable transport layer. The project is written in Go and is aimed at users who need a low-level tunnel that can operate in restricted or heavily filtered network environments. It is described as an alpha-stage tool, so compatibility and protocol behavior may change between releases. ...

...Its documentation provides server and client examples, usage parameters, best practices, troubleshooting notes, and performance testing information. The library is positioned as stable enough for real projects and has been used in online production scenarios. It is useful for Java backend developers who need low-latency network transport without giving up reliability features.

...In HTTP mode when the server received some data it can't just send them to the client directly because HTTP is not bi-directional, instead, the server must wait until the client requests them, which means these data will be stored in memory for some time.