Simple Text Oriented Messaging Protocol for interoperable messaging. Connect to RabbitMQ, ActiveMQ, and any STOMP-compatible broker from your Delphi applications.
Quick answer: sgcWebSockets adds STOMP messaging through the TsgcWSPClient_STOMP component, which you attach to a TsgcWebSocketClient, so Delphi and C++ Builder apps can subscribe, send, run transactions and negotiate heart-beats over WebSocket against RabbitMQ, ActiveMQ or any STOMP broker.
STOMP provides a simple, text-based messaging protocol that enables interoperability between different message brokers and client implementations.
STOMP is designed to be simple and easy to implement. Unlike binary protocols, STOMP uses a text-based frame format that is human-readable and straightforward to debug. It defines a small set of commands — CONNECT, SEND, SUBSCRIBE, UNSUBSCRIBE, ACK, NACK, BEGIN, COMMIT, ABORT, and DISCONNECT — that cover all common messaging patterns. sgcWebSockets implements the STOMP protocol over WebSocket connections, enabling browser and native clients to communicate with enterprise message brokers.
Enterprise messaging made simple with a clean, text-based protocol.
Human-readable frames make debugging and development straightforward. Each frame consists of a command, headers, and an optional body.
Fully compatible with RabbitMQ and ActiveMQ message brokers, providing access to enterprise messaging infrastructure.
Clean command set covering connection management, message sending, and topic subscription with clear semantics.
Request receipt confirmations from the broker to ensure your messages have been received and processed successfully.
Group multiple SEND and ACK operations into atomic transactions with BEGIN, COMMIT, and ABORT commands.
Automatic keep-alive mechanism to detect broken connections and maintain persistent broker sessions.
Enterprise messaging scenarios where STOMP provides simple, reliable communication.
Connect Delphi applications to enterprise message queues for reliable, asynchronous communication between systems.
Enable loosely-coupled communication between microservices using topic-based messaging and queue patterns.
Build event-driven systems where components react to events published through STOMP message brokers.
Bridge communication between applications written in different languages and frameworks through a common protocol.
Connect to a STOMP broker, subscribe to a destination, and send messages.
uses
sgcWebSocket, sgcWebSocket_Classes, sgcWebSocket_Protocols;
var
WSClient: TsgcWebSocketClient;
STOMP: TsgcWSPClient_STOMP;
procedure TForm1.FormCreate(Sender: TObject);
begin
WSClient := TsgcWebSocketClient.Create(nil);
WSClient.Host := 'broker.example.com';
WSClient.Port := 15674;
// Configure STOMP protocol
STOMP := TsgcWSPClient_STOMP.Create(nil);
STOMP.Client := WSClient;
// The component offers the STOMP subprotocols itself,
// v12.stomp, v11.stomp and v10.stomp, taken from Versions
STOMP.Versions.V1_2 := True;
STOMP.Versions.V1_1 := True;
STOMP.Versions.V1_0 := False;
STOMP.Authentication.Enabled := True;
STOMP.Authentication.UserName := 'guest';
STOMP.Authentication.Password := 'guest';
STOMP.Options.VirtualHost := '/';
STOMP.HeartBeat.Enabled := True;
STOMP.HeartBeat.Outgoing := 10000;
STOMP.HeartBeat.Incoming := 10000;
// Set up event handlers
STOMP.OnSTOMPConnected := OnSTOMPConnected;
STOMP.OnSTOMPMessage := OnSTOMPMessage;
end;
procedure TForm1.ButtonConnectClick(Sender: TObject);
begin
WSClient.Active := True;
end;
procedure TForm1.OnSTOMPConnected(Connection: TsgcWSConnection;
Version, Server, Session, HeartBeat, RawHeaders: String);
begin
// Subscribe to a queue, the first argument is the subscription id
STOMP.Subscribe('sub-orders', '/queue/orders');
end;
procedure TForm1.OnSTOMPMessage(Connection: TsgcWSConnection;
MessageText, Destination, MessageId, Subscription, ACK, ContentType,
RawHeaders: String);
begin
// Process incoming messages
Memo1.Lines.Add(Destination + ': ' + MessageText);
end;
procedure TForm1.ButtonSendClick(Sender: TObject);
begin
// Send a message to a destination
STOMP.Send('/queue/orders',
'{"orderId": 12345, "status": "new"}');
end;Common questions about connecting Delphi and C++ Builder applications to STOMP brokers.
TsgcWebSocketClient and a TsgcWSPClient_STOMP, set the client Host and Port, then assign STOMP.Client := WSClient. The STOMP component offers the WebSocket subprotocol itself, v12.stomp, v11.stomp or v10.stomp according to its Versions property, so you never set a subprotocol by hand. After connecting you call STOMP.Subscribe to receive frames and STOMP.Send to publish to a destination. The component implements the STOMP commands CONNECT, SEND, SUBSCRIBE, ACK, NACK, BEGIN, COMMIT, ABORT and DISCONNECT.STOMP.HeartBeat.Outgoing and STOMP.HeartBeat.Incoming to keep the connection alive and detect dropped sessions. STOMP runs over the WebSocket transport for browser-compatible messaging.