Asynchronous services example codes

Found in: epoc32ex\Base\IPC\Async\SingleRequest

This example shows how to issue and wait for a single request.

The example shows the general principles involved in asynchronous programming. It uses a simple wait loop and shows how the completion of asynchronous events are handled without active objects.

This example deliberately does not use active objects.

Run the example either under WINS or on the ARMI platform.

• TRequestStatus : Asynchronous request status

Found in: epoc32ex\Base\IPC\Async\WaitLoop

This example shows how a wait loop can be used to identify and handle a completed request.

It shows the general principles involved in asynchronous programming. It uses a simple wait loop and shows how the completion of asynchronous events are handled without active objects.

This example deliberately does not use active objects.

Run the example either under WINS or on the ARMI platform.

• TRequestStatus : asynchronous request status

Found in: epoc32ex\Base\IPC\Async\RealLifeWaitLoop

As with the WaitLoop example, this example shows how a wait loop can be used to identify and handle a completed request. However, this example shows how the wait loop can deal with multiple asynchronous service providers.

The example shows the general principles involved in asynchronous programming; it uses a simple wait loop and shows how the completion of asynchronous events are handled without active objects.

This example deliberately does not use active objects.

Run the example either under WINS or on the ARMI platform.

• TRequestStatus : asynchronous request status

Found in: epoc32ex\Base\IPC\Async\RunComplete

The example shows how active objects and an active scheduler can be used to handle asynchronous events. Compare this with the following examples; SingleRequest, WaitLoop and RealLifeWaitLoop.

It demonstrates a single CMessageTimer active object which runs until completion.

Run the example either under WINS or on the ARMI platform.

• TRequestStatus : asynchronous request status

• CActiveScheduler : the active scheduler

• CActive : active object abstraction

• CTimer : timer base class (used here as a source of events)

Found in: epoc32ex\Base\IPC\Async\AcceptInputX

These examples show how active objects and an active scheduler can be used to handle asynchronous events.

They demonstrate a single CKeyMessengerProcessor active object (derived from class CActiveConsole), which accepts input from keyboard, but does not print it. This object contains a CMessageTimer object which it activates if the user inputs the character "m" and cancelled if the user inputs "c".

Run the example either under WINS or on the ARMI platform.

• TRequestStatus : asynchronous request status

• CActiveScheduler : the active scheduler

• CActive : active object abstraction

• CTimer : timer base class (used here as a source of events)

Found in: epoc32ex\Base\IPC\Async\FibonacciX

These examples show how active objects and an active scheduler can be used to handle asynchronous events and long-running services to maintain system responsiveness.

Run the example either under WINS or on the ARMI platform.

• TRequestStatus : asynchronous request status

• CActiveScheduler : the active scheduler

• CActive : active object abstraction

• CTimer : timer base class (used here as a source of events)