Event-Driven Architecture in Oorian

Oorian's event system is central to building interactive applications. Understanding how events flow helps you build better architectures.

Event Flow

1. User action in browser (click, type, etc.)
2. Oorian client captures event
3. Event sent to server via configured transport
4. Server-side listener invoked
5. UI updates sent back to browser

Event Types

• MouseClickedEvent: Button and element clicks
• InputChangeEvent: Text input changes (debounced)
• InputCompleteEvent: Input loses focus or Enter pressed
• FormEvent: Form submission
• KeyPressedEvent: Key presses on elements

Custom Events

Wrapper libraries define their own events (RowSelectedEvent, ChartClickEvent, etc.) following the same patterns.

Conclusion

Oorian's event system is familiar to Java developers—implement listener interfaces and register for events. The framework handles all browser-to-server communication transparently.