wps-events

Asynchronous communication between Go components is implemented using the Wave Terminal Publish-Subscribe (WPS) event system with a broker pattern for routing events. It enables different application parts to notify each other about changes without direct coupling.

A WaveEvent in the WPS pubsub system consists of an event type, scopes, sender information, persistence settings, and a data payload. This structure ensures events are properly routed and carry type-safe contextual data for subscribers.

Publishing and subscribing to events in Go using WPS involves calling designated publish functions with or without scopes, including asynchronous options, and setting up subscription handlers in your Go code. Detailed examples guide routing events to the correct listeners.

Best practices for event-driven architecture in Wave Terminal include using namespaces for event types, avoiding blocking operations, ensuring type-safe data payloads, properly scoping events, documenting events, and configuring event persistence appropriately.

Scoped events in the WPS event system should be used when you need to restrict event delivery to specific contexts or listeners, such as limiting notifications to a particular window or component rather than broadcasting globally to all subscribers.