MCCEExtensionInterface Class Reference

class MCCEExtensionInterface

Plug-in extension feature provider. E.g telephony engine might have plugin features specific to call providers functionality. Plug-in specific actions can be requested syncronous or asyncronous via this class. Async message results are returned using MCCEExtensionObserver One instance of extension interface is used in CCE. In CCP many (one for every plug-in). One is used in order to avoid using an array in CCE interface and to notify disapearance of that interface in case plug-in goes down.

Since
S60 3.2

Constructor & Destructor Documentation

~MCCEExtensionInterface()

~MCCEExtensionInterface ( ) [protected, inline, virtual]
Protected destructor. Object cannot be deleted from client.
Since
S60 3.2

Member Functions Documentation

CancelRequest(TUint32, TInt)

TInt CancelRequest ( TUint32 iServiceId,
TInt aRequestId
) [pure virtual]
Cancels request. See MCCEExtensionInterface::RequestCommand for explanation of service-id handling.
Since
S60 3.2

Parameters

TUint32 iServiceId
TInt aRequestId Id of request to cancel.

RequestCommand(TUint32, TInt, TDesC8 &)

TInt RequestCommand ( TUint32 iServiceId,
TInt aRequestId,
TDesC8 & aData
) [pure virtual]
Request a custom command. Results are returned via MCCEExtensionObserver . Many service-ids may map to same plug-in. Request-id is used for plug-in internal id of the request. Replies use also a service-id, but if e.g. one plug-in uses two service-ids 10 and 11 then request might use 10 and reply use 11. The request id is the id used to determine what the request and respone relate to. Service-id is used as routing information in CCE and its client.
Since
S60 3.2

Parameters

TUint32 iServiceId
TInt aRequestId Id of request.
TDesC8 & aData Request data.