How the Task Flows (Magic xpa 3.x)
Let's take a closer look at what is going on when this task operates.
Keep in mind that the actual "Customer List" client program would normally be running somewhere else, not on your server machine. That means the program doesn't have access to the database directly; nor, necessarily, to the Windows environment. However, it isn't a Citrix-style "screen scraper" either. Instead, some operations are executed in the client environment, and some are executed in the server environment. While this all happens automatically, it is important for you to know what is happening so you can optimize your programs if needed.
|
Initialization Phase
|
Server
|
A new context is created for this task.
|
|
Task Prefix
|
Server
|
Before the client task starts, the Magic xpa engine on the server opens the database tables, initializes the Virtual variables and using the Range and Locate values, creates the initial Data view.
The client task hasn't started yet. All operations execute on the server.
|
|
User Interaction
|
Client and Server
|
While the user is working with the task, the .NET engine will be working with the local XML that was sent, to execute operations and display data.
However, some operations will also be executed on the server, where needed.
During the User Interaction phase, Record Prefix and Suffix are executed according to the same criteria used for Online tasks. The client doesn't need to fetch a record from the server each time since a group of records was sent in the initialization of the task.
|
|
Task Suffix
|
Client and Server
|
The Rich Client task has already terminated. Operations that are executed can be executed on either the client or the server, depending on the operation. After the Task Suffix is finished, there is access to the server to close the task there.
|
We'll take a look at how the various handlers work in the Performance Awareness section.
