STOMP 1.2

The STOMP (Simple Text Oriented Messaging Protocol) 1.2 implementation provides text-based interoperability for messaging clients.
It is well-suited for environments where human-readable frames and protocol simplicity are preferred.

Features

• Text-based protocol with a simple frame structure
• Version 1.2 supported
• Heart-beating to detect idle/disconnected peers
• Message acknowledgments (ACK/NACK)
• Optional Base64 encoding for binary payloads

Configuration

Example:

protocols:
  stomp:
    version: "1.2"
    port: 61613
    heart_beat: "10000,10000"
    maxBufferSize: 65535
    maxReceive: 1000
    base64EncodeBinary: true

Parameters

Field	Type	Default	Description
version	String	1.2	STOMP protocol version.
port	Integer	61613	Port to listen for STOMP connections.
heart_beat	String	10000,10000	Heartbeat interval (client, server) in ms.
maxBufferSize	Integer	65535	Maximum STOMP frame buffer size.
maxReceive	Integer	1000	Maximum receive limit for frames.
base64EncodeBinary	Boolean	true	Whether to Base64 encode outgoing binary payloads. If false, assumes plain text payloads.

Notes

• STOMP is designed to be simple and human-readable, making it easier to debug than binary protocols.
• Base64 encoding ensures binary data can be carried safely, but adds overhead. Disable it if your clients can handle binary payloads directly.
• The STOMP configuration integrates seamlessly with other MAPS protocols, allowing bridging to MQTT, AMQP, NATS, and more.