Enterprise Integration Zone is brought to you in partnership with:

Principal Consultant at TIBCO Software with more than 15 years of experience in service-oriented architecture, enterprise application integration and application development. Marcelo is a DZone MVB and is not an employee of DZone and has posted 7 posts at DZone. You can read more from them at their website. View Full User Profile

An Introduction to STOMP

  • submit to reddit
STOMP (Simple (or Streaming) Text-Oriented Messaging Protocol) is a simple text-oriented protocol, similar to HTTP.

STOMP provides an interoperable wire format that allows clients to communicate with almost every available message broker. STOMP is easy to implement and gives you flexibility since it is language-agnostic, meaning clients and brokers developed in different languages can send and receive messages to and from each other. There are lots of server implementations that support STOMP (mostly compliant with the STOMP 1.0 specification). The following is a list of STOMP 1.0 compliant message servers:

On the client side, there are many implementations for a vast number of technologies. Below, you will find the libraries available for the most popular languages.
Language Libraries
C libstomp - http://stomp.codehaus.org/C
C++ Apache CMS - http://activemq.apache.org/cms/
C# and .Net Apache NMS - http://activemq.apache.org/nms/
Flash as3-stomp - http://code.google.com/p/as3-stomp/
Java Gozirra - http://www.germane-software.com/software/Java/Gozirra/
Objective-C objc-stomp - https://github.com/juretta/objc-stomp
Perl Net::Stomp::Client - http://search.cpan.org/dist/Net-STOMP-Client/ Net::Stomp - http://search.cpan.org/dist/Net-Stomp/
PHP stomp - http://www.php.net/manual/en/book.stomp.php stomp-php - http://stomp.fusesource.org/documentation/php/book.html
Python stomper - http://code.google.com/p/stomper/ stomp.py - http://code.google.com/p/stomppy/
Ruby on Rails stomp gem - https://rubygems.org/gems/stomp  activemessaging - http://code.google.com/p/activemessaging/
STOMP is an alternative to other open messaging protocols such as AMQP (Advanced Message Queueing Protocol) and implementation specific wire protocols used in JMS (Java Message Service) brokers such as OpenWire. It distinguishes itself by covering a small subset of commonly used messaging operations (commands) rather than providing a comprehensive messaging API.  Because STOMP is language-agnostic and easy to implement, it’s popular to application developers and technical architects alike. STOMP is also text-based. Since it does not use binary protocols like other message brokers, a wide range of client technologies work with STOMP, like Ruby, Python, and Perl. STOMP is simple to implement, but supports a wide range of core enterprise messaging features, such as authentication, messaging models (point to point and publish and subscribe), message acknowledgement, transactions, message headers and properties, etc.
Published at DZone with permission of Marcelo Jabali, author and DZone MVB. (source)

(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)