DE.SETF.AMQP: a Common Lisp client library for AMQP

de.setf.amqp implements a native Common Lisp client library for the 'Advanced Message Queueing
Protocol'. The implementation comprises wire-level codecs, implementations
for the standard protocol objects and methods, a functional interface for message-,
stream- and object-based i/o, and a device-level simple-stream implementation.

The library targets the revisions of the published AMQP protocol as of versions
0.8, 0.9, and 0.10. This means that it should work with respective RabbitMQ,
Apache ActiveMQ, and Qpid implementations. The implementation architecture
should also accommodate a control structure appropriate for the prospective
1.0 version - as least as described in preliminary drafts.
For each version, a distinct package comprises the object and method
definitions for protocol entities and codecs as generated from the respective
specification documents.[1] Each collection is a
complete projection, which means there is some amount of duplication.
The package and directory names names follow more-or-less the naming conventions of the
xml protocol documents[2]:

AMQP-1-1-0-8-0

version 0.8

[amqp0-8.xml, amqp0-8.pdf (2006-06)]

AMQP-1-1-0-9-0

version 0.9

[amqp0-9.xml, amqp0-9.pdf (2006-12)]

AMQP-1-1-0-9-1

version 0.9r1

[amqp0-9-1.xml, amqp0-9-1.pdf (2008-11-24)]

AMQP-1-1-0-10-0

version 0.10

[amqp.0-10.xml, amqp.0-10.pdf (2008-02-20)]

In order to modify the translation and/or generate new codecs consult the :de.setf.amqp.tools component.

All protocol versions are expressed through a common interface[3] which is specialized for the common
abstract classes. The initial connection phase determines the correct concrete connection implementation
to be used to communicate with the broker. Given which the other concrete object and method classes are
elected from the same package. One determines the version support directly by loading the respective
version's .asd file, which makes its connection class available for negotiation.

Status

This is intended as the base for a distributed semantic store.
What one has here is a reasonably complete engineering prototype.
It consumes phenomenal amounts of memory and runs astonishingly slowly:
5 - 10 milliseconds and 1 to 10 thousand bytes per round trip.
A request entails ten levels of generic function dispatch, half of which require keyword processing.
A response call stack is about as deep, but with somewhat less keyword processing.
As almost everything between the interface commands and the frame buffers is generated code, once it is clear
which aspects should remain available for specialization and/or optional arguments, the protocol call
stack would benefit from recasting uninteresting elements as ordinary functions of fixed arguments - depending
on implementation type, by a factor of ten to sixty.

It would also be nice to generate a table similar to RabbitMQ's to
record protocol conformance and compatibility with brokers. Eventually.
The present tests are limited to

Which, as an aside, illustrates that brokered messages persist between connections until they have been consumed.
Of which a default QPID broker with no persistence support was observed to cache only about 500k bytes
(ca. 25,000 messages of 20 bytes each).

com.b9.puri.ppcre @github/lisp :
This version modifies the original to replace the parser with
a cl-ppcre implementation which supports userinfo and to add an argument to merge-uri for non-strict
scheme merging.

Obtain the de.setf.amqp source and that for the de.setf.utility library

Obtain and load asdf, add the
hierarchical names utility.
If running MCL, with an asdf version that includes mandatory output translations, either disable it or
otherwise ensure that it doesn't choke on the default binding for user-homedir-pathname.

Place the libraries in a source tree to mirror their global identity as reflected in the required system
names, and add the root of this tree to the asdf registry. If the central registry entry is a logical
pathname, the hierarchical naming mechanism should suffice to map binaries to a "shadow" directory at the
root of the source tree. The bordeaux-threads -> alexandria reference is
unqualified, and as such, requires additional registration.

Licensing

This version is released under version 3 of the GNU Affero license (GAL).[5]
The required components are included as per the respective licenses and covered,
in this combined form, under the GAL as well