Link against: SensrvClient.lib
#include <sensrvdatalistener.h>
This class is for use with the CSensrvChannel::StartDataListeningL() method. Clients wishing to use data listening must inherit from this class and provide a reference to an instance of it in CSensrvChannel::StartDataListeningL().
Public Member Functions | |
| virtual void | DataReceived (CSensrvChannel &aChannel, TInt aCount, TInt aDataLost)=0 |
| Callback implemented by a client so that they can be notified that data is available to read. | |
| virtual void | DataError (CSensrvChannel &aChannel, TSensrvErrorSeverity aError)=0 |
| Callback implemented by a client so that they can be notified when data listening has failed. | |
| virtual void | GetDataListenerInterfaceL (TUid aInterfaceUid, TAny *&aInterface)=0 |
| Callback to future proof this API so that additional callbacks can be added in the future without breaking binary compatibility. | |
| ||||||||||||
|
Callback implemented by a client so that they can be notified when data listening has failed. If the error is fatal the channel will be closed, the sensor server session has been terminated and the channel object is no longer useable. If the error is minor, some data has potentially been lost, however listening is still active. Clients providing an implementation for this callback must ensure that the operation does not leave. If a leave does occur then the behaviour is undefined.
|
| ||||||||||||||||
|
Callback implemented by a client so that they can be notified that data is available to read. A client can read the data using CSensrvChannel::GetData(). Data is valid until this DataReceived() notification occurs again. Data loss can occur if the client does not retrieve data, using SensrvChannel::GetData(), from server fast enough after the client has been told it is availble. This can happen when system is under heavy load and the client process has lower priority than sensor server process. If data loss is a problem consider using a higher object count in data listening, which will reduce the number of IPC context switches. Clients providing an implementation for this callback must ensure that the operation does not leave. If a leave does occur then the behaviour is undefined.
|
| ||||||||||||
|
Callback to future proof this API so that additional callbacks can be added in the future without breaking binary compatibility.
|