Asynchronous activities are treated almost identically to synchronous activities,
the only difference being in the point at which the CHECK ACTIVITY command
is issued. Typically, for a synchronous activity, the CHECK ACTIVITY command
is issued immediately after the RUN or LINK command. For an asynchronous activity,
it might, for example, be issued:
- When the parent is reattached due to the firing of the activity’s
completion event.
- When the requestor is reattached due to the expiry of a timer. This could
occur if the requestor expects the activity to return without completing;
the requestor may then reactivate the activity by sending it an input event.
[[ Contents Previous Page | Next Page Index ]]