The NAT traversal stack: STUN, TURN and ICE as client and server, the UDP transports underneath them, and the Delphi side of RTCPeerConnection. Eight 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.
| ICE ClientTsgcICEClient — RFC 8445 Interactive Connectivity Establishment client; combines STUN and TURN to pick the best peer-to-peer path. | Read PDF | |
| RTCPeerConnectionTsgcRTCPeerConnection — Delphi-side RTCPeerConnection implementation paired with the W3C WebRTC API for browser interop. | Read PDF | |
| STUN ClientTsgcSTUNClient — RFC 8489 Session Traversal Utilities for NAT client; binding requests for peer-public-address discovery. | Read PDF | |
| STUN ServerTsgcSTUNServer — RFC 8489 STUN server for sgcWebSockets; lets behind-NAT peers discover their public reflexive address. | Read PDF | |
| TURN ClientTsgcTURNClient — RFC 8656 Traversal Using Relays around NAT client; allocates a relayed address and relays traffic when direct paths fail. | Read PDF | |
| TURN ServerTsgcTURNServer — RFC 8656 TURN relay server for sgcWebSockets; relays peer-to-peer traffic when ICE cannot establish a direct path. | Read PDF | |
| UDP ClientTsgcUDPClient — low-level UDP datagram client for sgcWebSockets P2P stack; foundation for STUN, TURN and ICE. | Read PDF | |
| UDP ServerTsgcUDPServer — low-level UDP datagram server for sgcWebSockets P2P stack; foundation for STUN, TURN and ICE. | 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.
12 documents
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.
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.
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.