STOMP provides an interoperable wire format so that STOMP clients can communicate with any STOMP message broker to provide easy and widespread messaging interoperability among many languages, platforms and brokers.
STOMP is a very simple and easy to implement protocol, coming from the HTTP school of design; the server side may be hard to implement well, but it is very easy to write a client to get yourself connected. For example you can use Telnet to login to any STOMP broker and interact with it!
The protocol is broadly similar to HTTP, and works over TCP using the following commands:
CONNECT
SEND
SUBSCRIBE
UNSUBSCRIBE
BEGIN
COMMIT
ABORT
ACK
NACK
DISCONNECT
Communication between client and server is through a “frame” consisting of a number of lines. The first line contains the command, followed by headers in the form <key>: <value> (one per line), followed by a blank line and then the body content, ending in a null character. Communication between server and client is through a MESSAGE, RECEIPT or ERROR frame with a similar format of headers and body content.
Implementations
These are some MOM products that support STOMP Protocol:
STOMP servers
STOMP clients
STOMP Servers
Name | Description | Compliance |
Apache ActiveMQ | the most popular and powerful open source messaging and Integration Patterns server | 1.01.1 |
Apache ActiveMQ Artemis | Apache ActiveMQ Artemis has a proven non blocking architecture. It delivers outstanding performance. | 1.01.11.2 |
Apache Apollo | a redesigned version of ActiveMQ | 1.01.11.2 |
CoilMQ | a lightweight pure Python STOMPbroker inspired by StompServer | 1.0 |
Gozirra | a lightweight Java STOMPbroker | 1.0 |
HornetQ | puts the buzz in messaging | 1.0 |
MorbidQ | a STOMPbased publish/subscribe server with absolutely no potential to cluster | 1.0 |
RabbitMQ | an Erlang-based, multi-protocol broker with full support forSTOMP via a plugin | 1.01.11.2 |
Sprinkle | written in Python and runs on Unix type platforms | 1.0 |
Stampy | a Java implementation of the STOMP1.2 specification | 1.2 |
StompConnect | provides a bridge to any other JMS provider | 1.0 |
StompServer | a lightweight pure Ruby STOMPserver | 1.0 |
STOMP Clients
Name | Language | Description | Compliance |
activemessaging | Ruby | an attempt to bring the simplicity and elegance of Rails development to the world of messaging | 1.0 |
AnyEvent::STOMP | Perl | a lightweight event-driven STOMPclient | 1.0 |
Apache CMS | C++ | is a JMS-like API for C++ | 1.0 |
Apache NMS | C# and .Net | a JMS-like API for .Net | 1.0 |
as3-stomp | Flash | an actionscript 3 implementation of the STOMPprotocol | 1.0 |
delphistompclient | Delphi and FreePascal | a STOMPclient for Embarcadero Delphi and FreePascal | 1.0 |
dstomp | Dynamic C | a STOMPclient library written in Dynamic C for Rabbit | 1.0 |
Gozirra | Java | a lightweight implementation of the STOMPspecification | 1.0 |
hxStomp | Haxe | a TCP socket-based STOMPprotocol client library written for the Haxe language | 1.0 |
libstomp | C | an APR based C library | 1.0 |
Net::Stomp | Perl | a Streaming Text Orientated Messaging Protocol client | 1.0 |
Net::STOMP::Client | Perl | STOMPobject oriented client module | 1.01.11.2 |
objc-stomp | Obkective C | a simple STOMP client based on AsynSocket | 1.0 |
POE::Component::Client::Stomp | Perl | a Perl extension for the POE Environment | 1.0 |
onstomp | Ruby | client library for message passing with brokers that support the STOMPprotocol | 1.01.1 |
The Tech Platform
コメント