Fixed lots of issues with installing a low-caps version of fshell from SIS file.
* Fixed issue in CCommandFactory whereby some APIs like GetCommandInfoL could trigger allocations on the wrong heap or signals to the wrong thread. The symptoms were often seen as a crash in the which_00 thread when running ciftest.
* Lots of build fixes for when FSHELL_PROTECTED_UIDS isn't defined and when all capabilities aren't available.
* Added new platform.mmh macro FSHELL_OPEN_SIGNED.
* Open signing of fshell SIS files is now supported for production S60 handsets. Build fshell with the FSHELL_OPEN_SIGNED macro defined (and without defining FSHELL_CAP_ALL or FSHELL_PROTECTED_UIDS) in your platform.mmh and submit \epoc32\fshell\fshell.unsigned.sis to https://www.symbiansigned.com/app/page/public/openSignedOnline.do . The following commands are not available when using Open Signing due to Platform Security restrictions: fdb; kerninfo; chunkinfo; svrinfo; objinfo; sudo; fsck; localdrive; ramdefrag; readmem; reboot; setcritical; setpriority. Others such as chkdeps, e32header, ps, and fshell itself will run but in a restricted capacity (for example, fshell will no longer allow you to modify files in the \sys\bin directory).
* Removed commands objinfo, svrinfo, chunkinfo, readmem, fsck completely when memory access isn't present - previously they would still appear in the help but would give an error if you tried to run them.
// SensibleClient.h
//
// Copyright (c) 2006 - 2010 Accenture. All rights reserved.
// This component and the accompanying materials are made available
// under the terms of the "Eclipse Public License v1.0"
// which accompanies this distribution, and is available
// at the URL "http://www.eclipse.org/legal/epl-v10.html".
//
// Initial Contributors:
// Accenture - Initial contribution
//
#ifndef SENSIBLECLIENT_H
#define SENSIBLECLIENT_H
#include <e32std.h>
class CServerCallbackDispatcher;
class TServerCallback;
class TCallbackParser;
/* This class is designed to be usable in a handle-body implementation. Ie you can hide the use of RSensibleSessionBody
* from your clients by declaring a TUint32 iPimpl[3] (or somesuch) in your client class, and constructing a subclass of
* RSensibleSessionBody with appropriate definitions of DoCreateSession and DoSendReceive that call into the real session
* object.
*
* You can also derive directly from RSensibleSessionBody if you're not fussed about hiding the implementation.
*/
NONSHARABLE_CLASS(RSensibleSessionBody)
{
friend class CServerCallbackDispatcher;
public:
RSensibleSessionBody();
protected:
void Close();
TInt Connect(TInt aMessageSlots, TBool aStartCallbackDispatcher);
TInt StartCallbackDispatcher(); // If not already started
void StopCallbackDispatcher();
virtual void DispatchCallbackL(TServerCallback& aCallback, TCallbackParser& aParser);
virtual void ServerDiedL();
// These have to be implemented by a derived class to call through to the session proper
virtual TInt DoCreateSession(const TDesC &aServer, const TVersion &aVersion, TInt aAsyncMessageSlots)=0;
virtual TInt DoSendReceive(TInt aFunction, const TIpcArgs &aArgs) const=0;
virtual void DoSendReceive(TInt aFunction, const TIpcArgs &aArgs, TRequestStatus &aStatus) const=0;
protected:
CServerCallbackDispatcher* iDispatcher;
};
#endif