// STRYKE-ZMQ — ENGINEERING REPORT

>_EXECUTIVE SUMMARY

stryke-zmq is an opt-in connector package in the stryke ecosystem. ZeroMQ client for stryke — the brokerless messaging library covering request/reply, publish/subscribe, push/pull pipeline, and dealer/router patterns.

libzmq is the C library every ZeroMQ binding wraps. It (plus libsodium) is vendored into the cdylib from source via zeromq-src and statically linked, so the published artifact has no system shared-library dependency.

~ARCHITECTURE

In-process cdylib design: the stryke side is a thin .stk library; the heavy code is a Rust cdylib dlopened on first use Zmq. stryke core never links against libzmq.

$SOCKET PATTERNS

Transports: tcp://, ipc://, inproc://, and multicast pgm:// / epgm://.

@FUNCTION FAMILIES

The 62 Zmq::* functions split into socket ops (require a live handle, cross the FFI boundary to libzmq) and pure helpers (validation/endpoint/topic/table utilities that create no socket).

&WHY OPT-IN (NOT BUILTIN)

libzmq is the canonical native ZeroMQ library. Bundled here as an opt-in stryke package so workflows that need it don't bloat the core binary. The trade-off is intentional — the core stryke binary stays slim precisely because each connector ships separately. Daily-driver work (one-liners, awk replacement, data scripting) doesn't need ZeroMQ, Kafka, or database drivers linked in.

/FFI PROTOCOL

JSON over the FFI boundary. Each export takes a JSON-encoded args dict (a C string) and returns a JSON object (a C string the caller frees with stryke_free_cstring). Sockets are referenced by an integer handle returned from zmq__socket.

# create a socket -> handle
{"type":"rep","bind":"tcp://*:5555"}  ->  {"handle":1,"type":"rep"}

# send / recv
{"handle":1,"data":"pong"}            ->  {"ok":true,"bytes":4}
{"handle":2,"timeout_ms":1000}        ->  {"data":"pong","bytes":4}

# timeout (not an error) and error shapes
{"timeout":true}
{"error":"unknown socket handle: 99"}

%SCOPE

See the README's "Why this is a package" and API reference for the authoritative scope. v0.17.0 covers socket lifecycle (create/close/bind/connect/unbind/disconnect, socket_pair, socket_count), send/recv (single, multipart, recv_more, non-blocking drain, sendrecv), pub/sub topic filters, the full socket-option table (set/get), poll/poll_many/events readiness, socket-event monitoring (monitor/monitor_recv), a backgrounded proxy device, binary-safe hex/base64 payloads, the Z85 codec + CURVE key generation (curve_keypair, curve_public, valid_curve_key; CURVE auth via curve_* options), context io_threads tuning, a one-shot REQ convenience (request), and pure topology/endpoint/table helpers (endpoint_bind_to_connect, endpoint_connect_to_bind, valid_endpoint, build_subscription, parse_subscription, topic_overlaps, prune_subscriptions, subscription_diff, socket_caps_all, parse_monitor_event). Open roadmap: a streaming recv callback loop for long-running SUB/PULL consumers and a higher-level steerable-proxy control helper (PAUSE/RESUME/TERMINATE).

#PROJECT METADATA