BEFORE YOU BUY

Two Things Worth Knowing First

What sgcHTTP needs from you, and what it does not. Both answers are short.

sgcHTTP is self-contained

Standalone, the sgcWebSockets Core runtime is included: the HTTP/TLS client stack every component sends its requests through, and the JSON layer that decodes Google Cloud responses. One SKU, one installer.

Full source code ships with every license, so all five clients and the runtime under them step through in your own debugger rather than disappearing into a binary.

Add-on required for two of five

HTTP/2 & gRPC need sgcCustomIndy

HTTP/2 negotiates the h2 protocol with ALPN during the TLS handshake, and the standard Indy library that ships with RAD Studio does not support ALPN. sgcHTTP's HTTP/2 client and gRPC client are built on sgcCustomIndy instead, which is added to your cart automatically when you order sgcHTTP. Already own a license? Remove it at checkout.

The three Google Cloud clients, Pub/Sub, Calendar and Firebase Cloud Messaging, are plain HTTPS. They run on the bare Core runtime and do not need sgcCustomIndy at all.

WHAT IS IN THE BOX

Two Palette Components, Three Google Cloud Clients

The HTTP/2 client and the gRPC client are non-visual components on the SGC HTTP palette page, declared in the sgcHTTP unit. Drop one on a form or create it in code, set the connection options, wire the events, then call the typed request methods. The three Google Cloud clients live in the same unit as code-only classes, there is nothing to drop on a form: create one, set GoogleCloudOptions, and call its methods directly.

HTTP/21 component

Multiplexed streams over one TLS connection

TsgcHTTP2Client speaks HTTP/2 (RFC 9113): multiple requests share a single TCP connection as independent streams, so one slow response does not block the others behind it. Headers are compressed with HPACK, and the h2 protocol is negotiated during the TLS handshake through ALPN, the reason the component is built on sgcCustomIndy rather than the standard Indy library. Every verb is covered, Connect, Get, Post, Put, Patch, Delete and Options, each with a synchronous call and an Async twin. Events surface the connection lifecycle: OnHTTP2Connect, OnHTTP2Response, OnHTTP2ResponseFragment for chunked bodies, OnHTTP2PushPromise for server push, OnHTTP2GoAway and OnHTTP2Disconnect. HTTP2Options configures the local settings frame, and TLSOptions and Authentication carry over from the rest of the sgc HTTP stack.

TsgcHTTP2Client Requires sgcCustomIndy

gRPC1 component

Unary and streaming RPC on the HTTP/2 client

TsgcGRPCClient is built on the HTTP/2 client, so it inherits the multiplexed connection and adds the gRPC wire format on top: length-prefixed Protocol Buffers messages over HTTP/2 streams. Call and CallAsync cover unary RPCs, ServerStreamingCall handles a stream of responses to one request, and OpenClientStream/SendStreamMessage/CloseClientStream plus OpenBidiStream/SendBidiMessage/CloseBidiStream cover client-streaming and bidirectional-streaming RPCs. OnGRPCResponse, OnGRPCStreamMessage and OnGRPCStreamEnd deliver the traffic, and RetryPolicy, Interceptors and ServiceConfig add retry behavior, cross-cutting logic and service configuration without touching the call sites. Like the HTTP/2 client it is built on, it needs sgcCustomIndy for ALPN.

TsgcGRPCClient Requires sgcCustomIndy

Google Cloud3 classes

Pub/Sub, Calendar and push notifications, plain HTTPS

Three more classes reach Google Cloud services over plain HTTPS, authenticated with a Google service account, and none of them need sgcCustomIndy. TsgcHTTPGoogleCloud_PubSub_Client publishes and pulls messages and manages topics, subscriptions and snapshots: Publish, Pull, Acknowledge, CreateTopic, CreateSubscription and the rest of the Pub/Sub REST surface. TsgcHTTPGoogleCloud_Calendar_Client wraps the Google Calendar API v3: NewCalendar, NewEvent, LoadEvents and LoadCalendars, with OnGetCalendar and OnGetCalendarEvent events for synchronization. TsgcHTTPGoogleCloud_FCM_Client sends a push notification payload to a Firebase project with one call, SendMessage. All three are code-only classes: create one, set GoogleCloudOptions, call the methods.

TsgcHTTPGoogleCloud_PubSub_Client TsgcHTTPGoogleCloud_Calendar_Client TsgcHTTPGoogleCloud_FCM_Client

HOW IT WORKS

Two Dependencies, Not Five

The five classes split cleanly by what they need underneath. HTTP/2 and gRPC need ALPN, which means sgcCustomIndy. Google Cloud needs nothing beyond HTTPS and a service account, which the bundled Core runtime already provides.

HTTP/2 needs ALPN, so it needs sgcCustomIndy

Application-Layer Protocol Negotiation picks h2 during the TLS handshake, and the standard Indy library that ships with RAD Studio has no ALPN support. TsgcHTTP2Client is built on sgcCustomIndy, eSeGeCe's custom Indy build, instead.

gRPC is Protocol Buffers riding on the HTTP/2 client

TsgcGRPCClient does not open its own connection, its Client property is a TsgcHTTP2Client. Unary, server-streaming, client-streaming and bidirectional calls all travel as HTTP/2 streams underneath.

Google Cloud is HTTPS plus a service account

The three Google Cloud clients authenticate with GoogleCloudOptions.JWT, a Google service account's project id, client email and private key, and call the REST APIs over the Core runtime's plain HTTPS stack. OnAuthToken and OnAuthTokenError surface the token exchange.

The Core runtime is in the box

Standalone, the sgcWebSockets Core runtime is included. It contributes the HTTP/TLS client stack every one of the five clients calls through, and its full source is part of the package like everything else.

QUICK START

HTTP/2 and gRPC, Side by Side

Both components are declared in the sgcHTTP unit, and TsgcGRPCClient carries its own HTTP/2 connection through its Client property. The same code compiles in Delphi 7 to 13 and C++ Builder.

uses
  sgcHTTP;

var
  HTTP2: TsgcHTTP2Client;
  GRPC: TsgcGRPCClient;
begin
  // HTTP/2: multiplexed requests over one TLS connection
  HTTP2 := TsgcHTTP2Client.Create(nil);
  HTTP2.Host := 'https://api.example.com';
  HTTP2.OnHTTP2Response := HTTP2Response;
  HTTP2.Active := True;

  HTTP2.GetAsync('/v1/status');

  // gRPC: built on the HTTP/2 client, unary and streaming RPC
  GRPC := TsgcGRPCClient.Create(nil);
  GRPC.Client.Host := 'https://grpc.example.com';
  GRPC.OnGRPCResponse := GRPCResponse;

  GRPC.CallAsync('example.OrderService', 'GetOrder', RequestBytes);
end;

procedure TForm1.HTTP2Response(Sender: TObject;
  const Connection: TsgcHTTP2ConnectionClient;
  const Request: TsgcHTTP2RequestProperty;
  const Response: TsgcHTTP2ResponseProperty);
begin
  Memo1.Lines.Add(Response.DataString);
end;

procedure TForm1.GRPCResponse(Sender: TObject;
  const aResponse: TsgcGRPCResponse);
begin
  Memo1.Lines.Add(aResponse.DataString);
end;

// include: sgcHTTP.hpp

// HTTP/2: multiplexed requests over one TLS connection
TsgcHTTP2Client *HTTP2 = new TsgcHTTP2Client(this);
HTTP2->Host = "https://api.example.com";
HTTP2->OnHTTP2Response = HTTP2Response;
HTTP2->Active = true;

HTTP2->GetAsync("/v1/status");

// gRPC: built on the HTTP/2 client, unary and streaming RPC
TsgcGRPCClient *GRPC = new TsgcGRPCClient(this);
GRPC->Client->Host = "https://grpc.example.com";
GRPC->OnGRPCResponse = GRPCResponse;

GRPC->CallAsync("example.OrderService", "GetOrder", RequestBytes);

void __fastcall TForm1::HTTP2Response(TObject *Sender,
    const TsgcHTTP2ConnectionClient* Connection,
    const TsgcHTTP2RequestProperty* Request,
    const TsgcHTTP2ResponseProperty* Response)
{
  Memo1->Lines->Add(Response->DataString);
}

void __fastcall TForm1::GRPCResponse(TObject *Sender,
    const TsgcGRPCResponse* aResponse)
{
  Memo1->Lines->Add(aResponse->DataString);
}

PLATFORMS

One Dependency for Two Clients, None for Three

The HTTP/2 client and the gRPC client build on sgcCustomIndy, which covers the same platform range as sgcWebSockets itself. The Google Cloud clients are plain HTTPS, so they run wherever the Core runtime does.

TsgcHTTP2Client & TsgcGRPCClient Built on sgcCustomIndy for ALPN

Windows Win32 Windows Win64 Linux64 macOS iOS Android

Google Cloud clients Plain HTTPS, no sgcCustomIndy needed

Windows Win32 Windows Win64 Linux64 macOS iOS Android

IDE support One source tree, design-time packages per version

Delphi 7 to 13 C++ Builder

Trial installer The sgcWebSockets All-Access trial includes the sgcHTTP components

One download, all five classes

Download the trial installer →

PRICING

A Standalone Package

sgcHTTP is licensed on its own, starting at €249 for a single developer. All licenses include full source code, 1 year of updates and a 50% to 70% renewal discount: 50% when you renew one pack, 60% for two, 70% for three or more. sgcAI, sgcMQ, sgcSocial, sgcCustomIndy, sgcAuth and sgcHTTP each count as a pack. sgcHTTP is also included in the All-Access bundle.

sgcHTTP

€249

Single, Team and Site licenses available.

HTTP/2 client with multiplexing & HPACK
gRPC client, unary & streaming RPC
Google Cloud Pub/Sub, Calendar & FCM clients
sgcWebSockets Core runtime included
Delphi 7 to 13 & C++ Builder
Full source code
1 year of updates

HTTP/2 and gRPC need the sgcCustomIndy add-on. Checkout adds it automatically, and you can remove it if you already own a license.

Buy Single License €249

Team €399 Site €649

Checkout lists three items: the sgcWebSockets Core runtime entitlement, charged at zero, the sgcHTTP pack itself, and the sgcCustomIndy add-on, added automatically. Full pricing details.

Other Products by eSeGeCe

Pair sgcHTTP with our other Delphi, C++ Builder and .NET component libraries.

sgcCustomIndy

The custom Indy library sgcHTTP's HTTP/2 and gRPC clients are built on: ALPN, TLS 1.3 and static OpenSSL linking.

Learn more →

sgcWebSockets

The full library: WebSocket clients and servers, HTTP/2, gRPC, IoT, P2P and AI components. Its Enterprise edition includes gRPC too.

Learn more →

sgcAI

AI, LLM and MCP components. One chat component reaches OpenAI, Anthropic, Gemini, DeepSeek, Ollama, Grok and Mistral.

Learn more →

sgcMQ

Native MQTT 3.1.1/5.0, AMQP 0.9.1, AMQP 1.0, Apache Kafka and STOMP client components, with the Core runtime bundled.

Learn more →

sgcSocial

WhatsApp Business Cloud API and Telegram TDLib client components, with the Core runtime bundled.

Learn more →

sgcQUIC

QUIC (RFC 9000) and HTTP/3 (RFC 9114) client and server components built on the native OpenSSL 3.5 QUIC engine.

Learn more →

sgcHTTP: HTTP/2, gRPC & Google Cloud Components for Delphi & C++ Builder

Two Things Worth Knowing First

sgcHTTP is self-contained

HTTP/2 & gRPC need sgcCustomIndy

Two Palette Components, Three Google Cloud Clients

Multiplexed streams over one TLS connection

Unary and streaming RPC on the HTTP/2 client

Pub/Sub, Calendar and push notifications, plain HTTPS

Two Dependencies, Not Five

HTTP/2 and gRPC, Side by Side

One Dependency for Two Clients, None for Three

A Standalone Package

sgcHTTP

Modern HTTP, gRPC and Google Cloud from Native Code

Other Products by eSeGeCe

sgcCustomIndy

sgcWebSockets

sgcAI

sgcMQ

sgcSocial

sgcQUIC