Streaming Text Oriented Messaging Protocol

From HandWiki - Reading time: 2 min


Short description: Communications protocol
Streaming Text Oriented Messaging Protocol
Communication protocol
PurposeMessage-oriented middleware
IntroducedError: first parameter is missing. ()
OSI layerApplication layer (Layer 7)

Simple (or Streaming) Text Oriented Message Protocol (STOMP), formerly known as TTMP, is a simple text-based protocol, designed for working with message-oriented middleware (MOM). It provides an interoperable wire format that allows STOMP clients to talk with any message broker supporting the protocol.[1][2]

Overview

The protocol is broadly similar to HTTP, and works over TCP using the following commands:[3]

  • 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.

Example

SEND
destination:/queue/a
content-type:text/plain

hello queue a
^@

Implementations

Some message-oriented middleware products support STOMP,[4] such as::

References





Licensed under CC BY-SA 3.0 | Source: https://handwiki.org/wiki/Streaming_Text_Oriented_Messaging_Protocol
1 |
↧ Download this article as ZWI file
Encyclosphere.org EncycloReader is supported by the EncyclosphereKSF