stomp-patterns: Stompl MOM Stomp Patterns
|Dependencies||base (>=4.0 && <=5.0), bytestring (>=0.10.4.0), containers (>=0.4.2.1), mime (>=0.3.3), mtl (>=2.1.2), split (>=0.2.2), stomp‑queue (>=0.1.4), stompl (>=0.1.0), time (>=1.4) [details]|
|Copyright||Copyright (c) Tobias Schoofs, 2013 - 2015|
|Maintainer||tobias dot schoofs at gmx dot net|
|Category||Network, Message-oriented Middleware, Stomp, Client|
|Uploaded||by TobiasSchoofs at Tue Aug 4 18:45:13 UTC 2015|
|Downloads||670 total (7 in the last 30 days)|
|Rating||(no votes yet) [estimated by rule of succession]|
|Status||Docs available [build log]
Last success reported on 2015-08-04 [all 1 reports]
Hackage Matrix CI
The Stomp Protocol specifies a reduced message broker with queues usually read by one application and written by one or more applications. The specification does not include other, more advanced, interoperability patterns, where, for example, a client requests a job from a server or a publisher sends data to many subscribers. Such communication patterns, apparantly, are left to be implemented by applications. Patterns like client-server, publish and subscribe and many others, however, are used over and over again in message-oriented applications.
This library implements a number of communication patterns on top of the Stomp specification that are often used and often described in the literature. There is a set of basic patterns,
publish and subscribe and
as well as a set of derived patterns, namely:
Desk: A service to obtain the access point (i.e. queue name) of a specified provider;
Load balancers: Services to balance requests among a group of connected workers (a.k.a. Majordomo pattern);
Bridge: Connections between brokers.
The notion of pattern and the related concepts, as they are presented here, rely heavily on Pieter Hintjens, "Code Connected", O'Reilly, 2013 (see also http://hintjens.com/books).
For package maintainers and hackage trustees