diff -r 4816d766a08a -r f345bda72bc4 Symbian3/PDK/Source/GUID-6A6E5F25-BAA0-5D12-AB93-87A0E8A206BD.dita --- a/Symbian3/PDK/Source/GUID-6A6E5F25-BAA0-5D12-AB93-87A0E8A206BD.dita Tue Mar 30 11:42:04 2010 +0100 +++ b/Symbian3/PDK/Source/GUID-6A6E5F25-BAA0-5D12-AB93-87A0E8A206BD.dita Tue Mar 30 11:56:28 2010 +0100 @@ -1,14 +1,14 @@ - - - - - -ArchitectureThis topic describes the architectural relationship between the telephony watcher classes.

The telephony watcher is contains two main components:

- Telephony Watcher Framework - Architectural Relationships -

In the diagram the core low level functionality is the publish and subscribe mechanism. The client applications must use the RProperty functions to get the notifications. Telephony watcher functionality is the watcher framework.

The watcher framework

The watcher framework is provided by watcher.exe. The watcher and the plug-in run in the same thread. The telephony watcher framework does the following:

  • creates and starts the plug-in objects

  • provides an asynchronous interface for the plug-ins

  • creates the communication link with the telephony server to get the information

  • maintains the plug-ins and the watcher framework in the same thread

  • provides updates to the client applications

  • provides error corrections in the communication between the watcher framework and the telephony server

  • uses the comms debug utility to log the events

  • deletes the plug-in objects

Watcher Plug-ins

The watcher plug-ins are loaded by the watcher framework. The plug-ins are implemented as DLLs. The primary functions of the watchers are to monitor the telephony activities and publish the information with the publish and subscribe. The two watcher plug-ins are:

  • Signal Strength Watcher

  • Call Indicator Watcher

Telephony Watchers \ No newline at end of file + + + + + +ArchitectureThis topic describes the architectural relationship between the telephony watcher classes.

The telephony watcher is contains two main components:

+ Telephony Watcher Framework - Architectural Relationships +

In the diagram the core low level functionality is the publish and subscribe mechanism. The client applications must use the RProperty functions to get the notifications. Telephony watcher functionality is the watcher framework.

The watcher framework

The watcher framework is provided by watcher.exe. The watcher and the plug-in run in the same thread. The telephony watcher framework does the following:

  • creates and starts the plug-in objects

  • provides an asynchronous interface for the plug-ins

  • creates the communication link with the telephony server to get the information

  • maintains the plug-ins and the watcher framework in the same thread

  • provides updates to the client applications

  • provides error corrections in the communication between the watcher framework and the telephony server

  • uses the comms debug utility to log the events

  • deletes the plug-in objects

Watcher Plug-ins

The watcher plug-ins are loaded by the watcher framework. The plug-ins are implemented as DLLs. The primary functions of the watchers are to monitor the telephony activities and publish the information with the publish and subscribe. The two watcher plug-ins are:

  • Signal Strength Watcher

  • Call Indicator Watcher

Telephony Watchers \ No newline at end of file