Proposal: Events — remaining work

The event system is implemented — see Events for the full, current model (typed DTOs, events.publish(topic, dto), typed listener (e: T) on "topic", the type-erased envelope, the default in-memory MemoryBus/MemoryConsumer with no serialization, and replaceable external transports via Events.encode/decode/dispatch). This page tracks only the parts not yet built.

Open items

• Primitive number/bool arrays in payloads. Done. Integer[], Number[], and Bool[] (alongside String[] and arrays of event types) now work as payload fields — the runtime defines the primitive array typedefs and the derived codec encodes them element-by-element.

• Async / buffered delivery. Done (basic). Events.runAsync() drains the (now thread-safe) queue on a background worker thread and dispatches to listeners; Events.stop() ends it. Richer policies (batching, retries, dead-letters) can still be layered as a custom ConsumerService.

• The topic inside the listener. A listener receives the typed DTO only. For wildcard subscriptions (one listener over several topics) it may also want the concrete topic that fired — e.g. a second optional parameter or an accessor.

• Schema / version negotiation on the wire. External transports serialize by the event's type name; evolving an event's shape across producer/consumer versions has no built-in versioning story yet.

• Multiple external buses at once. Routing different event topics to different bound transports (rather than a single PublisherService) is not yet expressible.

Background

The original design notes (string topics with Json payloads, and an earlier Events.emit builtin) have been superseded by the typed model described in Events, which is the source of truth.