Stomp

Stomp

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.

Stomp is a simple text-based protocol supported by the ActiveMQ Broker that allows communication from a variety of clients (e.g. C++, Java, .NET, Ruby, Python, etc).

It provides an interoperable wire format that allows STOMP clients to talk with any message broker supporting the protocol. It is thus language-agnostic, meaning a broker developed for one language or platform can receive communications from client software developed in another language.

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 : (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.


Stomp
added 5 years 9 months ago

Contents related to 'Stomp'

Simple Object Access Protocol (SOAP): SOAP, originally defined as Simple Object Access Protocol, is a protocol specification for exchanging structured information in the implementation of Web Services in computer networks.

- IPython
- Bootstrap
- Apache Pig
- Apache Cassandra
- Jenkins
- Nginx Server
- Continuous Integration
- Threading Building Blocks (TBB)
- Message Passing Interface (MPI)
- Language-Integrated Query (Linq)
- Maven
- Element Management System (EMS)
- Asynchronous JavaScript and XML (AJAX)
- Transport Layer Security (TLS), Secure Sockets Layer (SSL)
- GlassFish
- Virtual Destinations
- Stomp
- Process Templates
- Apache Portable Runtime (Apr)
- Java Message Service (JMS)
5
4
3
2
1