stomp, stomper, stompest!¶
The STOMP client in this package is dead simple: It does not assume anything about your concurrency model (thread vs process) or force you to use it any particular way. It gets out of your way and lets you do what you want. The package also consists of a generic set of components each of which you may use independently to roll your own STOMP client:
- a wire-level STOMP frame parser and compiler,
- a faithful implementation of the syntax of the STOMP protocol with a simple stateless function API,
- a generic implementation of the STOMP session state semantics, such as protocol version negotiation at connect time, transaction and subscription handling (including a generic subscription replay scheme which may be used to reconstruct the session’s subscription state after a forced disconnect),
- and a failover transport URI scheme akin to the one used in ActiveMQ.
This package is thoroughly unit tested and production hardened for the functionality used by the current maintainer and by Mozes – persistent queueing on ActiveMQ. Minor enhancements may be required to use this STOMP adapter with other brokers.
The asynchronous client is based on Twisted, a very mature and powerful asynchronous programming framework. In order to keep the stompest package self-consistent, the asynchronous client is available as a separate package stompest.async.
You may install this package in any of the following ways:
pip install stompest, or
python setup.py install.
This is the latest version of the documentation and is generated from the latest commit on the main branch. If you are looking for documentation which is consistent to a specific release, you may download the corresponding tarball for offline browsing. If someone is willing to (teach me how to) set up release specific documentation on PyPI, please go ahead!