UNIX-socket boundary: accepts hook arrivals and hands each decoded event to an injected dispatch fn.
The dispatch fn is an argument rather than a direct hive-events call, so
the accept loop is exercised in tests against a recording fn and carries no
dependency on the event system it feeds.
UNIX-socket boundary: accepts hook arrivals and hands each decoded event to an injected dispatch fn. The dispatch fn is an argument rather than a direct `hive-events` call, so the accept loop is exercised in tests against a recording fn and carries no dependency on the event system it feeds.
(start! socket-path dispatch!)Bind SOCKET-PATH and serve arrivals to DISPATCH! until stopped.
Returns a map carrying the server and the accept thread; pass it to
stop!. A stale socket file is removed first: bind fails on an existing
path, and a path under the addon's own runtime directory belongs to a dead
predecessor rather than to a live peer.
Bind SOCKET-PATH and serve arrivals to DISPATCH! until stopped. Returns a map carrying the server and the accept thread; pass it to `stop!`. A stale socket file is removed first: `bind` fails on an existing path, and a path under the addon's own runtime directory belongs to a dead predecessor rather than to a live peer.
(stop! {:keys [server running socket-path]})Close the listener started by start! and unlink its socket file.
Idempotent: stopping an already-stopped listener is a no-op rather than an error, so addon shutdown need not track whether start succeeded.
Close the listener started by `start!` and unlink its socket file. Idempotent: stopping an already-stopped listener is a no-op rather than an error, so addon shutdown need not track whether start succeeded.
cljdoc builds & hosts documentation for Clojure/Script libraries
| Ctrl+k | Jump to recent docs |
| ← | Move to previous article |
| → | Move to next article |
| Ctrl+/ | Jump to the search field |