diff -r 80ef3a206772 -r 48780e181b38 Symbian3/SDK/Source/GUID-5C215C64-5D3D-5B65-A11F-BE6F8C306CF4.dita --- a/Symbian3/SDK/Source/GUID-5C215C64-5D3D-5B65-A11F-BE6F8C306CF4.dita Fri Jul 16 17:23:46 2010 +0100 +++ b/Symbian3/SDK/Source/GUID-5C215C64-5D3D-5B65-A11F-BE6F8C306CF4.dita Tue Jul 20 12:00:49 2010 +0100 @@ -79,4 +79,4 @@
The resource (
Note: These UIDs can be the same.
The following illustration shows how the SIP Client Resolver subsystem resolves the target client implementation and requests the resolved client to connect to the SIP implementation. In this plan, the default resolution logic is applied.
The following list describes how the target client is resolved using
The user receives a SIP request and the target client is defined using
The user requests the SIP Client Resolver API implementation for a channel UI to connect to the user.
The user requests the target client to connect to SIP with the resolved UID if there is no connection with the resolved channel UID.
The SIP Client Resolver API implementation starts the target client.
The following list describes how the target client is resolved using
The user receives a SIP request and the target client is defined using
The user requests the SIP Client Resolver API implementation for a channel UI to connect to the user.
The user requests the target client to connect to SIP with the resolved UID if there is no connection with the resolved channel UID.
The SIP Client Resolver API implementation starts the target client.