Priority events
Priority Events
Start here when listener order is part of correctness and event work needs explicit phases.
- Priority types
- Slots
- Invocation
- Safety
Use this section when event listener order is part of correctness. Priority events keep the event model, but add explicit priority slots for deterministic phases.
AzPriorityEventNo-payload ordered phases and the priority mental model.AzPriorityEvent<T>Ordered dispatch with small values, references, or cheap-to-copy payloads.AzPriorityEventRef<T>Ordered readonly-ref dispatch for large struct payloads.Slots And SubscriptionsSlot conventions, subscription APIs, tokens, and bags.InvocationNormal, fast, safe, selective, and masked invocation.Safety And ThreadingException handling, cancellation, off-thread behavior, and re-entrancy.Patterns, Performance, And APICommon patterns, pitfalls, metrics, defaults, and quick reference.
Recommended Reading Order
- Start with AzPriorityEvent.
- Pick AzPriorityEvent<T> or AzPriorityEventRef<T> when ordered payload dispatch matters.
- Use Slots And Subscriptions before designing phase names.
- Use Invocation and Safety And Threading when tuning behavior.