Expand description
Durable work queue types. Durable work queue — types shared across host components and the SDK.
Layer: L0 — these types live in yeti-types because the unified
Context references QueuePayload via the queue_enqueue
signature.
Structs§
- QueueFn
- Host-side registry entry for a
#[queue_fn]discovered across loaded wasm apps. The worker dispatches by looking up(app_id, name)in theHashMap<(AppId, String), QueueFn>that the runtime maintains. - Queue
FnEntry - App-scoped queue-fn entry.
Enums§
- Queue
Payload - The work a queue item represents. Persists in
yeti-queueas msgpack inside thepayloadcolumn.
Traits§
- Wasm
Queue Invoker - Process-wide hook for routing queue jobs into wasm components.
Functions§
- lookup_
queue_ fn - Look up a host-local
QueueFnby name (ignoresapp_id— static-crate functions live in the same linker table as the host binary). - lookup_
queue_ fn_ for_ app - Look up a queue function for a specific app. Wraps the static-
inventory lookup in a
QueueFnEntryfor uniform return shape.app_idis unused today (every registeredqueue_fnlives in the host’s static inventory) but kept on the signature so dispatch sites don’t have to change if a per-app surface returns. - set_
wasm_ queue_ invoker - Install the process-wide wasm queue invoker. Idempotent —
subsequent calls are no-ops (
OnceLock). - wasm_
queue_ invoker - Get the installed wasm queue invoker, if any. yeti-queue’s dispatcher calls this on every Function-payload job to decide whether to route through wasm.