So, 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
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.
CL-RemiZMQ: CL-RemiZMQ

Ma conférence "Server Sent Events et ZeroMQ"

Mardi dernier (16 septembre), j’ai présenté une conférence au meetup organisé par l’AFUP Paris, sur les Server Sent Events (SSE) et la bibliothèque ZeroMQ.

Retrouvez les slides de la conférence dans l'article en lien.

https://www.geek-directeur-technique.com/2025/09/20/ma-conference-server-sent-events-et-zeromq
#php #sse #zeromq #afup

Ma conférence "Server Sent Events et ZeroMQ"

Mardi dernier (16 septembre), j'ai présenté une conférence au meetup organisé par l'AFUP Paris, sur les Server Sent Events (SSE) et la bibliothèque ZeroMQ. Les SSE reposent sur un protocole basé sur le HTTP, et dont l'implémentation est intégrée aux navigateurs via une API Javascript. Ce protocol

De geek à directeur technique

Here is my example of testing PyZMQ client and server code with pytest and pytest-mock. I haven't found much information on this topic. Anyone else have examples of testing PyZMQ code? https://gavinw.me/pythonic/pyzmq/test-client-server.html

#python #pytest #zeromq #pyzmq

Pythonic Programming

Testing a PyZMQ Client and Server

Chapter 4 - The ZeroMQ Process: C4 · Social Architecture

ooh a #zeromq-based project.. haven't seen that in a while https://github.com/zasper-io/zasper
GitHub - zasper-io/zasper: High Performace IDE for Jupyter Notebooks

High Performace IDE for Jupyter Notebooks. Contribute to zasper-io/zasper development by creating an account on GitHub.

GitHub

@b0rk In the interest of sharing failed hypotheses: I’m not finding evidence people use #zeromq for fire-and-forget, blind fanout queues or other spray-n-pray style uses.

For some reason I thought this was an explicit feature given the protocol design, but I’m not seeing it. It explicitly lacks reliable delivery, so an expert may know better.

cppzmq-tour/index.org at master · brettviren/cppzmq-tour

A tour of how to develop with cppzmq, the C++ bindings to ZeroMQ libzmq. - brettviren/cppzmq-tour

GitHub

So if I understand it right, there's no way to use #ZeroMQ with an existing event loop - I can't get the filehandles out of it to poll them myself.

There's also no way to bind multiple socket types (e.g. both a RES and a PUSH) to the same physical endpoint? So I'd need two different ones?

It seems like this library is far less useful than it first appears :(

My friends, I’ve spent an unreasonable amount of time debugging a #ZeroMQ issue whereby a router socket swallows a message: ‘zmq_msg_send’ succeeds but there’s no corresponding ‘sendto’ call in the strace log.

How would you go about debugging this?

(Other questions I ask myself: How did I end up here? Why am I even doing this⁈)