stomp-queue: Stompl Client Library
|Versions||0.0.1, 0.0.2, 0.0.3, 0.0.5, 0.0.6, 0.0.7, 0.0.8, 0.1.0, 0.1.1, 0.1.2, 0.1.3, 0.1.4, 0.2.0, 0.2.1, 0.2.2, 0.3.1|
|Dependencies||attoparsec (>=0.9.1.1), base (>=4.0 && <=5.0), bytestring (>=0.10), mime (>=0.3.3), network (>=188.8.131.52), split (>=0.1.4.1), stompl (>=0.1.1), time (>=1.1.4), utf8‑string (>=0.3.6) [details]|
|Copyright||Copyright (c) Tobias Schoofs, 2011 - 2014|
|Maintainer||tobias dot schoofs at gmx dot net|
|Category||Network, Message-oriented Middleware, Stomp, Client|
|Uploaded||by TobiasSchoofs at Tue Feb 18 22:00:51 UTC 2014|
|Downloads||5274 total (44 in the last 30 days)|
|Rating||(no votes yet) [estimated by rule of succession]|
|Status||Docs uploaded by user
Build status unknown [no reports yet]
Hackage Matrix CI
The Stomp Protocol specifies message-oriented interoperability. Applications connect to a message broker to send (publish) or receive (subscribe) messages through queues. Interoperating applications do not know the location or internal structure of each other. They see only each other's interfaces, i.e. the messages published and subscribed through the broker.
The Stomp Queue library provides
a Stomp client, using abstractions like
This basic abstractions are implemented in the module Queue.
The Patterns module adds an abstraction layer
on top of queues, in particular an implementation
of the client-server pattern.
- New Option for newWriter
- Minor changes:
Dependency for stompl-0.1.1
Some more enquiries into potential mem leaks, but more to follow
- Dependency for bytestring 0.10
- Major changes:
Compliance with Stomp 1.2:
There are major changes in the frame format, please refer to the documentation of the stompl package, version 0.1.0, there are important changes that may impact messages for older versions!
When generating an Ack frame, the id header is by default taken from the ack header in the corresponding Message frame. Should there be no ack header or if its value is empty, the value of the header message-id is taken. This behaviour complies with 1.2 for brokers supporting this version, but also continues to work with 1.1 brokers.
It is now possible to send a Stomp frame to connect to a broker (the broker, of course, has to accept Stomp frames and process them correctly). There is a new Copt (OStomp) to support this feature.
- Client/Server on top of Queues.
- Fighting with hackagedb...
- Heartbeats caused a memory leak by creating many Connection instances in the connection state list. The connections were lazily deleted, i.e. were not deleted at all. Connection state is now cleaned up by a strict delete.
- Major changes:
Underscore functions (withConnection_) removed;
New with* functions: withWriter, withPair;
New option for connection (ClientId);
Headers for broker-specific options can be passed to connection (this changes the withConnection type signature!)
- New interface writeAdHoc
- Minor corrections
- Initial release
For package maintainers and hackage trustees