Event-Driven Architecture (Magic xpa 3.x)
The benefits of developing event-based applications.
With Magic xpa you can better define your business logic using the event-driven architecture of the Magic xpa runtime engine. The event-driven programming paradigm lets you create full-featured applications with clearly defined logic.
An event-driven application can respond to any runtime occurrence generated by the end user or generated internally by the developer as part of the business logic.
Clearer Code – Using event-driven architecture, your business logic is neatly defined in each task for the event the task handles. This makes the task clearer, more understandable, and easier for other developers to maintain.
Responsive Application – Using event-driven architecture lets you better handle runtime occurrences generated by the end user or by third-party components, such as the database in use.
Code Re-use – Event-driven architecture lets you define your business logic as global logic you only need to define once and can reuse throughout your project. Having these sharable logic segments saves you the time of writing and maintaining repeated logic segments.
This concept paper covers the following subjects:
Events, Triggers, and Handlers
Event Handlers
Raising Events
Event Polling
Logic Units
User Events
Event Logic Unit Resources and Information
Handling Multi-marked Records
