The WebSocket client and server themselves, in Delphi and in .NET, together with the resilience components that guard them and the scaling components that put several servers behind one address. Twelve documents in this section, each one available as a web page and as an A4 PDF.
Read links open the web version. PDF links open the same content laid out for A4, with a cover page and fixed page breaks.
| WebSocket Client (Delphi)The TsgcWebSocketClient component — RFC 6455 WebSocket client for Delphi VCL, FireMonkey, Lazarus and FPC over TCP and TLS. | Read PDF | |
| WebSocket Server (Delphi)TsgcWebSocketServer / TsgcWebSocketHTTPServer — Delphi WebSocket and HTTP server, RFC 6455 compliant, with TLS, virtual hosts and protocol pipelines. | Read PDF |
| WebSocket Client (.NET)The .NET port of TsgcWebSocketClient — RFC 6455 WebSocket client for .NET Framework, .NET Core, .NET 5+ and .NET Standard. | Read PDF | |
| WebSocket Server (.NET)The .NET port of TsgcWebSocketHTTPServer — RFC 6455 WebSocket server with TLS and HTTP fall-back for .NET Framework, .NET Core and .NET 5+. | Read PDF |
| API Key ManagerCentralised API-key rotation, scoping and rate-limit accounting for sgcWebSockets API and HTTP components. | Read PDF | |
| Circuit BreakerCircuit-breaker resilience pattern for sgcWebSockets — automatic open/half-open/closed transitions wrap any HTTP or WebSocket call. | Read PDF | |
| FirewallIP-based firewall component for sgcWebSockets servers — block, allow-list and rate-limit by address and CIDR range. | Read PDF | |
| Rate LimiterPer-connection and per-key rate-limiting component — token bucket and fixed-window strategies for any sgcWebSockets server. | Read PDF |
| Multi-node ClusteringTsgcWSCluster — scale your sgcWebSockets servers across multiple nodes. A publish or Presence event on one node reaches subscribers connected to every other node, through a zero-infrastructure mesh backplane or a Redis Pub/Sub backplane. | Read PDF | |
| HTTP.sys API ServerTsgcWebSocketServer_HTTPAPI — kernel-mode (http.sys) HTTP and WebSocket server for the highest possible throughput on Windows. | Read PDF | |
| Load BalancerTsgcWebSocketLoadBalancerServer — pluggable load balancer for sgcWebSockets back-ends with sticky sessions and health checks. | Read PDF | |
| Proxy ServerTsgcWebSocketProxyServer — reverse-proxy for sgcWebSockets traffic with TLS termination, request rewriting and connection pooling. | Read PDF |
Eighty-six documents in all. The full index lists every one of them on a single page.
8 documents
Components that talk to language models and vector stores: the provider clients, the chatbot and translator front ends, embeddings, and both sides of the Model Context Protocol.
26 documents
Ready-made clients for third-party services. Mostly WebSocket market data and trading feeds, plus the messaging platforms and the two SignalR dialects.
3 documents
Bridges that host an existing WebBroker or DataSnap application on an sgcWebSockets server, so one executable answers REST, WebSocket and HTTP/2 on the same port.
14 documents
The HTTP/2 client and server, gRPC, the OAuth2 and JWT components on both sides, WebAuthn, and the push and queue services reached over plain HTTP.
2 documents
MQTT clients preconfigured for the two managed IoT brokers, with the authentication each one insists on already wired up.
8 documents
The NAT traversal stack: STUN, TURN and ICE as client and server, the UDP transports underneath them, and the Delphi side of RTCPeerConnection.
12 documents
WebSocket subprotocols and message brokers: MQTT, both AMQP versions, STOMP against two brokers, WAMP, WebRTC signalling, and the five custom sgc subprotocols.
1 document
Server-side components that answer a browser or platform specification rather than call somebody else’s service.