Clojurians Log v2

that's one on our to-do list - but yes, as you say, will require a different solution for the client-server model

for now, polling xt.txs is one option, yep, or (if you don't need the results of the XT transaction) we also know of people using XT as a downstream system from their own Kafka log - i.e. one golden-source Kafka topic feeds both a process that submits to XT and whatever other subscriptions you need

In my operational simplified world polling xt.txs seems OK. If I want some additional nicety and want to get on that hypetrain I could try integrating missionary to supervise the downstream consumption and cancel work, if a new tx arrived. But in reality I just need to watch a single table, like normal worker queues on postgres. Thanks!