Event System

• Event System Overview
  • Event System Concepts and Facilities
  • Application Event Loops
  • Processing Work on Event Threads
  • Event Loops in Application Parts
  • Connecting to Event Sources
  • Callback Ownership and Lifetime
  • Invocations and Timers
  • Simplifying Event Code with Bindings
  • Asynchronous Task Workflows
  • Communication Between Loops
  • Cancellation and Shutdown
  • Handling Event Failures
  • Keeping Loops Responsive Under Load
  • Owning Loop Execution
  • Extending the Event System
  • Related Topics
• Events in Erbsland Core
  • Event Loops and Targets
  • Callback Execution and Responsiveness
  • Invocations and Timers
  • State and Callback Lifetime
  • Event Sources and Notifications
  • Worker Threads and Application Parts
  • Choosing an Event-Based Design
• Running an Application with Event Loops
  • The Application’s Main Event Loop
    • Timer Setup and Repeated Work
    • Configuration Before Dispatch
    • Application Startup and Shutdown
  • Initialization and Cleanup Hooks
  • Worker Event Threads
  • Application Parts and Their Event Loops
• Processing Work on Event Threads
  • Result Ownership and Synchronization
  • Creating and Starting Managed Threads
  • Posting Work and Choosing a Result Target
  • Completion, Quit, and Join
  • Failure and Interrupted Work
  • Queue Limits and Cooperative Cancellation
• Using Event Loops in Application Parts
  • Registration and Automatic Startup
  • Configuration and Event-Owned Resources
  • Initialization and Asynchronous Readiness
  • Callback Execution and State Ownership
  • Cross-Thread Service Calls
  • Asynchronous Shutdown
  • Cleanup and Failure Paths
• Connecting to Event Sources
  • Creating a Source and Registering Handlers
  • Callback Execution Order
  • Source and Handler Lifetime
  • Event Targets and Event Editors
  • Replacing and Clearing Handlers
  • Operation Errors and Callback Exceptions
• Handling Event Failures
  • API Call Failures, Operation Errors, and Callback Exceptions
  • Operation Errors and Task Completion
  • Reporting Captured Callback Failures
  • Continuing, Quitting, or Failing the Application
  • Custom Callback Failure Handlers
  • Releasing a Caller Waiting for Worker Results
  • Exception Boundaries for Extension Authors
• Keeping Callbacks and Their Owners Alive
  • Source and Callback Ownership
  • Value Captures and Borrowed References
  • Weak Captures for Optional Recipients
  • Subscription Ownership
    • Cancellation and Running Callbacks
  • Cancellation Scope
  • Event Editor Lifetime
  • Releasing Sources from Callbacks
• Scheduling Work and Timers
  • Deferred Execution with invoke()
  • Delayed Invocations and Timer Handles
  • Fixed-Delay and Fixed-Rate Timers
  • Debouncing with Timer Restart
  • Timer Cancellation and Captured State
• Simplifying Event Code with Bindings
  • From Nested Callbacks to a Bound Continuation
  • Choosing the Receiving Loop
  • Passing Results to a Bound Method
  • Binding a Callable with Additional Context
  • Retaining an Operation While Its Display Disappears
  • Finishing Work After the User Quits
• Building Workflows Across Callbacks
  • From Individual Steps to One Operation
  • Advancing the Workflow from a Result
  • Returning Decisions to the Owner Loop
  • Ownership Across the Steps
  • Defining Completion for the Caller
• Communicating Between Event Loops
  • State Belongs to a Loop
  • A Running Main as the Reply Target
  • Target Lifetime and Recipient Lifetime
  • Replacing a Request Before Its Reply
  • Completion, Failure, and Responsiveness
• Cancelling Work and Shutting Down
  • Resource Completion Comes Before Loop Termination
  • Cancellation Belongs to the Operation
  • What Graceful Loop Quit Drains
  • Failure and Shutdown Deadlines
  • Ending and Joining Worker Threads
  • Application-Wide Shutdown
  • Required Completion After an Optional View Closes
• Keeping Event Loops Responsive Under Load
  • Bounding Outstanding Requests
  • Callback Duration and Shared Loop Time
  • Queue Capacity as an Overload Policy
  • A Deliberately Lossy Update Stream
  • Queue Overflow Failure and Waiting Policies
  • Interpreting Queue Counts and Delayed Work
• Driving Event Loops Directly
• Designing Objects That Produce Events
• Defining and Posting Typed Events
• Writing an Event Backend
• Integrating Native Waiting and Custom Drivers