The HTTP/2 client and server, gRPC, the OAuth2 and JWT components on both sides, WebAuthn, TOTP, LDAP, SAML, OpenID Connect and mail OAuth2, and the push and queue services reached over plain HTTP. Nineteen 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.
| Amazon SQS ClientAmazon SQS HTTP client — send, receive, delete and manage SQS messages from Delphi with AWS Signature v4. | Read PDF | |
| Apple Push Notification ServiceAPNs HTTP/2 client — send iOS and macOS push notifications from Delphi using token-based or certificate-based authentication. | Read PDF | |
| Google Calendar APIGoogle Calendar v3 API client — events, calendars, ACLs and notifications with OAuth 2.0 from Delphi. | Read PDF | |
| Google Cloud Pub/SubGoogle Cloud Pub/Sub REST client — publish to topics, pull from subscriptions and manage IAM bindings from Delphi. | Read PDF | |
| Firebase Cloud MessagingFirebase Cloud Messaging HTTP v1 client — send Android, iOS and web push from Delphi using OAuth 2.0 service-account credentials. | Read PDF | |
| gRPC ClientTsgcGRPCClient — native gRPC client over HTTP/2: unary and streaming calls, custom metadata, deadlines, compression, interceptors and automatic retry. | Read PDF | |
| HTTP/2 ClientTsgcHTTP2Client — RFC 9113 HTTP/2 client over TLS with ALPN, header compression (HPACK), multiplexing and stream prioritisation. | Read PDF | |
| HTTP/2 ServerTsgcWebSocketHTTPServer with HTTP/2 — RFC 9113 server-side HTTP/2 with ALPN, HPACK and server push. | Read PDF | |
| JWT ClientTsgcHTTP_JWT_Client — JSON Web Token client helper for any sgcWebSockets HTTP component. | Read PDF | |
| JWT ServerTsgcHTTP_JWT_Server — JSON Web Token server-side issuance and validation for sgcWebSockets HTTP and WebSocket servers. | Read PDF | |
| LDAP ClientTsgcLDAPClient: LDAP v3 and Active Directory client to authenticate users, search the directory and read group membership over LDAPS or StartTLS. | Read PDF | |
| Mail OAuth2TsgcMailOAuth2: OAuth2 tokens and SASL XOAUTH2 / OAUTHBEARER strings for SMTP, IMAP and POP3 with Microsoft 365 and Gmail. | Read PDF | |
| OAuth2 ClientTsgcHTTP_OAuth2_Client — OAuth 2.0 client with authorisation-code, PKCE, client-credentials, device-code and refresh-token flows. | Read PDF | |
| OAuth2 ProviderTsgcHTTP_OAuth2_Server_Provider — pre-built OAuth 2.0 provider adapters (Google, Microsoft, GitHub, etc.) for the OAuth2 client. | Read PDF | |
| OAuth2 ServerTsgcHTTP_OAuth2_Server — OAuth 2.0 authorisation-server implementation for sgcWebSockets HTTP / WebSocket servers. | Read PDF | |
| OpenID Connect ClientTsgcHTTP_OIDC_Client: OpenID Connect sign in with discovery, PKCE, nonce and strict ID token validation. | Read PDF | |
| SAML Service ProviderTsgcSAMLServiceProvider: SAML 2.0 single sign-on service provider with metadata, Redirect and POST bindings and full response validation. | Read PDF | |
| TOTP AuthenticatorTsgcTOTPAuthenticator: TOTP and HOTP one-time passwords for two-factor authentication, with QR provisioning, replay protection and recovery codes. | Read PDF | |
| WebAuthn ServerTsgcWSAPIServer_WebAuthn — W3C WebAuthn Level 2 server-side relying-party for sgcWebSockets HTTP servers. | Read PDF |
Ninety-one 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.
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.