CStartServer Class Reference

class CStartServer : public CActive

Starts a server process and asynchronously and synchronise with it.

The process must support synchronisation via Randezvous RStartServer

Inherits from

Constructor & Destructor Documentation

CStartServer(RAsyncConnectBase &, const TVersion &, TInt)

IMPORT_CCStartServer(RAsyncConnectBase &aAsyncConnectBase,
const TVersion &aVersion,
TIntaAsyncMessageSlots
)

Constructor

Parameters

RAsyncConnectBase & aAsyncConnectBasethe client side server object
const TVersion & aVersionthe desired version of the server
TInt aAsyncMessageSlotsnumber of messages to allocate in client server message queue

~CStartServer()

IMPORT_C~CStartServer()

Member Functions Documentation

Cancel()

IMPORT_C voidCancel()

Connect(const TDesC &, TRequestStatus &, TUint)

IMPORT_C voidConnect(const TDesC &aServerName,
TRequestStatus &aStatus,
TUintaAttempts = 3
)

The Start method

Connect the Handle to the Server and asynchronously starts the server if neccessary

Parameters

const TDesC & aServerNamename of the server, no file extension
TRequestStatus & aStatusa request of the client waiting for server to connect
TUint aAttempts = 3how many times to try to connect

Connect(const TDesC &)

voidConnect(const TDesC &aServerName)[protected]

Parameters

const TDesC & aServerName

DoCancel()

voidDoCancel()[protected, virtual]

Implements cancellation of an outstanding request.

This function is called as part of the active object's Cancel().

It must call the appropriate cancel function offered by the active object's asynchronous service provider. The asynchronous service provider's cancel is expected to act immediately.

DoCancel() must not wait for event completion; this is handled by Cancel().

CActive::Cancel

RunL()

voidRunL()[protected, virtual]

Handles an active object's request completion event.

A derived class must provide an implementation to handle the completed request. If appropriate, it may issue another request.

The function is called by the active scheduler when a request completion event occurs, i.e. after the active scheduler's WaitForAnyRequest() function completes.

Before calling this active object's RunL() function, the active scheduler has:

1. decided that this is the highest priority active object with a completed request

2. marked this active object's request as complete (i.e. the request is no longer outstanding)

RunL() runs under a trap harness in the active scheduler. If it leaves, then the active scheduler calls RunError() to handle the leave.

Note that once the active scheduler's Start() function has been called, all user code is run under one of the program's active object's RunL() or RunError() functions.

CActiveScheduler::Start CActiveScheduler::Error CActiveScheduler::WaitForAnyRequest TRAPD

Member Data Documentation

RAsyncConnectBase & iAsyncConnectBase

RAsyncConnectBase &iAsyncConnectBase[protected]

TInt iAsyncMessageSlots

TInt iAsyncMessageSlots[protected]

TUint iAttempts

TUint iAttempts[protected]

TRequestStatus * iClientStatus

TRequestStatus *iClientStatus[protected]

TUint iCounter

TUint iCounter[protected]

iCounter - counts the attempts to start the daemon

TBufC< KMaxFileNameLength > iName

TBufC< KMaxFileNameLength >iName[protected]

TInt iProcessStarting

TInt iProcessStarting[protected]

RStartProcess iStartProcess

RStartProcess iStartProcess[protected]

iStartProcess - RStartProcess to asynchronously start server

const TVersion & iVersion

const TVersion &iVersion[protected]