Mistress RemiliaSo, I have my own bindings for #ZeroMQ for #CommonLisp now: http://fossil.cyberia9.org/cl-remizmq/
Consider this the end of my vacation 
This isn't quite 0.1.0 yet, but is already usable. It's a much more complete set of bindings compared to cl-zmq. Things of particular note:
* There's a Low-Level API that has complete (or at least near-complete) low-level bindings for contexts, sockets, messages, atomics, timers and proxies. It also has more extensive knowledge of the error codes, socket options, CURVE stuff, capability detection, etc.
* There's a High-level API that wraps all of the low-level stuff in high-level CLOS classes and/or code.
* The timers are an exception, and were rewritten from scratch in native Lisp code in the High-level API so that they integrate better with Lisp ecosystems, and play nicer when using the REPL.
* The
There are some examples ported from the official guide in the repo. There is no documentation yet, but all of the functions/methods have documentation strings, which should hold you over until I write some actual docs.
Consider this the end of my vacation
This isn't quite 0.1.0 yet, but is already usable. It's a much more complete set of bindings compared to cl-zmq. Things of particular note:
* There's a Low-Level API that has complete (or at least near-complete) low-level bindings for contexts, sockets, messages, atomics, timers and proxies. It also has more extensive knowledge of the error codes, socket options, CURVE stuff, capability detection, etc.
* There's a High-level API that wraps all of the low-level stuff in high-level CLOS classes and/or code.
* The timers are an exception, and were rewritten from scratch in native Lisp code in the High-level API so that they integrate better with Lisp ecosystems, and play nicer when using the REPL.
* The
PROXY high-level class is nicer to use and more Lisp-y. It runs on its own thread so that you can use it in a REPL, and is easier to control.There are some examples ported from the official guide in the repo. There is no documentation yet, but all of the functions/methods have documentation strings, which should hold you over until I write some actual docs.