// the find
RRQM/TouchSocket
TouchSocket is an integrated .NET networking framework that includes modules for socket, TCP, UDP, SSL, named pipes, HTTP, WebSocket, RPC, and more. It offers a one-stop solution for TCP packet issues and enables quick implementation of custom data message parsing using protocol templates.
TouchSocket is a .NET networking library covering TCP/UDP/WebSocket/HTTP/MQTT/RPC and more, with a custom IOCP implementation that avoids the copy-to-secondary-buffer pattern from the Microsoft samples. It targets everyone from industrial Modbus/MQTT clients to game server developers who want packet framing handled for them. The primary audience is Chinese enterprise .NET developers — most community resources, issues, and supplemental docs are in Chinese.
The data adapter pipeline is genuinely well-designed: fixed-header, variable-header, and custom framing adapters are first-class, and hot-swapping them at runtime is a real feature most networking libs don't bother with. The memory model using ByteBlock and Memory<T> throughout means you can push high message rates without GC pressure biting you. The plugin system (reconnect, heartbeat, SSL, auth all via ConfigurePlugins) keeps the core thin while making common production requirements composable. Broad platform reach — .NET Framework 4.6.2, Standard 2.0, and modern .NET — means you can use it in legacy WinForms codebases and Unity without pulling in a second library.
The documentation site is primarily Chinese, and the English README is a surface-level translation; any non-trivial integration question will require reading Chinese docs or joining a QQ group, which is a real barrier for non-Chinese teams. The '10x faster throughput' benchmark claim in the README compares against the official Microsoft IOCP sample code, which is a deliberately simplified teaching example — not production-grade netcode — so the number is essentially meaningless. There is a paid 'Pro Edition' with undisclosed features gated behind it, which means the open-source version may be arbitrarily limited in ways that only surface after you've committed to it. Dmtp (the proprietary RPC/file-transfer protocol layered on top) is a bespoke protocol with no interop outside the TouchSocket ecosystem, so if your other services aren't also .NET with TouchSocket, that whole subsystem is dead to you.