×
Namespaces

Variants
Actions
Revision as of 17:45, 11 November 2012 by lpvalente (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Archived:Required capabilities for messaging components (MTM) in S60 3rd Edition

From Nokia Developer Wiki
Jump to: navigation, search

Archived.pngArchived: This article is archived because it is not considered relevant for third-party developers creating commercial solutions today. If you think this article is still relevant, let us know by adding the template {{ReviewForRemovalFromArchive|user=~~~~|write your reason here}}.

Article Metadata
Compatibility
Platform(s): S60 3rd Edition
S60 3rd Edition, Feature Pack 1
S60 3rd Edition FP1
S60 3rd Edition (initial release)
Article
Keywords: CBaseMtm
Created: User:Technical writer 2 (July 7, 2006, updated December 10, 2008)
Last edited: lpvalente (11 Nov 2012)

Description

S60 3rd Edition and S60 3rd Ed, FP1 devices impose heavy requirements for messaging DLLs in terms of platform security capabilites.

Solution

All client-side MTM components (Client MTM, UI MTM, and UI Data MTM DLLs) need to have ALL -TCB capabilities because they can be loaded by any application that can have any set of capabilities from that capability space.

A server-side MTM component, that is, an MTM DLL loaded by the messaging server, requires capabilities equal to the loading process. The server-side MTM component should have exactly these capabilities:

ReadDeviceData
WriteDeviceData
ProtServ
NetworkControl
 
 
NetworkServices
LocalServices
ReadUserData
WriteUserData

Given these heavy capability requirements, any (client-side) MTM implementation has to go through the Symbian Signed process and get manufacturer approval.

See also

ALL -TCB capabilities for client-side MTMs are no longer required from S60 3rd Edition, Feature pack onwards: Required capabilities for messaging components (MTM) (Known Issue)

This page was last modified on 11 November 2012, at 17:45.
46 page views in the last 30 days.