1 <?xml version="1.0" encoding="utf-8"?>

     2 <!-- Copyright (c) 2007-2010 Nokia Corporation and/or its subsidiary(-ies) All rights reserved. -->

     3 <!-- This component and the accompanying materials are made available under the terms of the License 

     4 "Eclipse Public License v1.0" which accompanies this distribution, 

     5 and is available at the URL "http://www.eclipse.org/legal/epl-v10.html". -->

     6 <!-- Initial Contributors:

     7     Nokia Corporation - initial contribution.

     8 Contributors: 

     9 -->

    10 <!DOCTYPE concept

    11   PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">

    12 <concept id="GUID-ACDED56F-38FE-491D-B019-BE2C53A75D28" xml:lang="en"><title>Data

    13 caging</title><prolog><metadata><keywords/></metadata></prolog><conbody>

    14 <p>Data caging means that the applications and the users have access only

    15 to certain areas of the file system. In practice the applications can access

    16 their own private folders and folders that are marked as open. It means, for

    17 example, that one application cannot access the private folder and data of

    18 another application. There are restricted file storage areas for system, private,

    19 and resource data.</p>

    20 <p>The file system has the following structure:</p>

    21 <ul>

    22 <li><p>The <codeph>\sys</codeph> folder is the restricted system

    23 area. You need <codeph>AllFiles</codeph> capability to read the content, and

    24 Trusted Computing Base (<codeph>TCB</codeph>) capability to modify the content.</p>

    25 <p>The subfolder <codeph>\sys\bin\</codeph> contains all binaries (<codeph>exe</codeph>, <codeph>dll</codeph>,

    26 etc.). All binaries must have a different name. An application can only be

    27 launched from this subfolder.</p></li>

    28 <li><p>The <parmname>\private\</parmname> folder includes folders

    29 for all applications.</p><p>The <codeph>\private\&lt;SID&gt;\</codeph> subfolder

    30 contains private data only to be accessed by the application itself. SID is

    31 determined by the <xref href="GUID-3B6E25F7-C1A8-461F-97F7-421DB559BC98.dita#GUID-3B6E25F7-C1A8-461F-97F7-421DB559BC98/GUID-EEC50FC0-46D5-4ED7-AD95-67430D5EC652">Secure

    32 Identifier</xref> of the process. Without any capabilities you can read and

    33 write only in the application's own directory. You need <codeph>AllFiles</codeph> capability

    34 to access all private directories. Backup software can read and write to this

    35 directory.</p><p>The <codeph>\private\&lt;SID&gt;\import\</codeph> subfolder

    36 is for resource files, such as registration files, that are not directly related

    37 to the application. You can write into this subfolder only after it is created

    38 and named correctly.</p><p>Application registration resource files should

    39 be installed in the <parmname>\private\10003a3f\import\apps</parmname> subfolder.</p>

    40 </li>

    41 <li><p>The <parmname>\resource</parmname> folder is for sharing

    42 resource files.  This data can be icons, bitmaps, and other material useful

    43 for all the applications. You do not need any capabilities to read these files.

    44 You need <codeph>TCB</codeph> capability to modify the content.</p><p>ECom

    45 registration resource files should be installed in the <parmname>\resource\plugins</parmname> subfolder.</p>

    46 </li>

    47 </ul>

    48 <p>For more information, see <xref href="jar:GUID-35228542-8C95-4849-A73F-2B4F082F0C44.jar!/sdk/doc_source/guide/Base-subsystem-guide/f32/FileServerClientSide/FileServerClientSideGuide5/ApplicationArchitecture.guide.html" format="application/java-archive">File

    49 locations</xref>.</p>

    50 </conbody></concept>