WebSocket subprotocols and message brokers: MQTT, both AMQP versions, STOMP against two brokers, WAMP, WebRTC signalling, and the five custom sgc subprotocols. 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.
| AMQP 0.9.1AMQP 0.9.1 client for Delphi, C++ Builder and .NET — speak natively to RabbitMQ and other 0.9.1-compatible brokers over TCP or WebSocket. | Read PDF | |
| AMQP 1.0AMQP 1.0 client for Delphi, C++ Builder and .NET — the OASIS-standardised messaging protocol used by Azure Service Bus, ActiveMQ Artemis and Apache Qpid. | Read PDF | |
| Custom Protocol — DatasetsgcWebSockets custom subprotocol that streams TDataset changes over WebSocket — server publishes updates, clients apply them automatically. | Read PDF | |
| Custom Protocol — End-to-End EncryptionEnd-to-end encrypted custom subprotocol — peer-to-peer keys never reach the server, perfect for sensitive payloads. | Read PDF | |
| Custom Protocol — FilesFile-transfer custom subprotocol — chunked, resumable upload and download over WebSocket with progress notifications. | Read PDF | |
| Custom Protocol — PresencePresence custom subprotocol — connection-state, channels and member metadata broadcast across the room, in the spirit of Pusher Channels. | Read PDF | |
| Custom Protocol — sgc (Generic PubSub)sgc generic publish-subscribe custom subprotocol — channels, queued messages and broker-style fan-out built into sgcWebSockets. | Read PDF | |
| MQTT ClientLightweight publish/subscribe messaging for Delphi, C++ Builder and .NET — full MQTT 3.1.1 and 5.0 support over TCP or WebSocket transports. | Read PDF | |
| STOMP (ActiveMQ)STOMP 1.2 client tuned for Apache ActiveMQ — destination prefixes, JMS-style headers and broker-specific features. | Read PDF | |
| STOMP (RabbitMQ)STOMP 1.2 client tuned for RabbitMQ — exchange destinations, queue conventions and RabbitMQ-specific headers. | Read PDF | |
| WAMP ProtocolRouted RPC and publish-subscribe over WebSocket for Delphi, C++ Builder and .NET. WAMP v1 client and server, JSON payloads carried over the wamp WebSocket subprotocol. | Read PDF | |
| WebRTC ProtocolWebRTC signalling server for browser-paired peer-to-peer audio, video and data channels — Delphi server pairs with the standard W3C WebRTC JavaScript API. | 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.
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.
1 document
Server-side components that answer a browser or platform specification rather than call somebody else’s service.