diff -r ebc84c812384 -r 46218c8b8afa Symbian3/PDK/Source/GUID-08007041-CE18-5B1C-9AE6-042EBBFD1AB6.dita --- a/Symbian3/PDK/Source/GUID-08007041-CE18-5B1C-9AE6-042EBBFD1AB6.dita Thu Mar 11 15:24:26 2010 +0000 +++ b/Symbian3/PDK/Source/GUID-08007041-CE18-5B1C-9AE6-042EBBFD1AB6.dita Thu Mar 11 18:02:22 2010 +0000 @@ -1,43 +1,43 @@ - - - - - -Preventing -Plug-in Overriding The plug-in framework supports two methods to prevent a RAM based -plug-in from overriding a ROM based plug-in. The first method is to use the -ROM-only resolver and the second method is to explicitly prevent a ROM-based -implementation from being overridden by a RAM-based implementation. -

Using the ROM-only -resolver restricts the search of the framework plug-ins to the ROM only.

Alternatively, -to prevent a RAM-based implementation from overriding a ROM-based implementation, -set the rom_only variable to 1 in the resource -registration file for the implementation.

- -Using the ROM-only resolver -

Use KRomOnlyResolverUid as the CResolver -UID passed to those variants of REComSession::ListImplementationsL() and REComSession::CreateImplementationL() that take the TUid aResolverUid parameter.

If an -installable upgrade to a ROM-based plug-in is correctly supplied by a vendor, -then the ROM-only resolver finds and uses the upgrade. Platform security controls -are used to ensure that the upgrade is secure. For details, see How to upgrade -ROM-based plug-ins securely.

- -Preventing a ROM-based implementation from being overridden: -

If the ROM-based plug-ins must be prevented from being overridden -by a RAM-based plug-in, use the version -2 resource file format.

In the .rss file, -the rom_only member of the IMPLEMENTATION_INFO structure -must be set to 1.

rom_only set to 1 indicates the -ROM-based implementation must be used.

rom_only set -to 0 indicates the ROM-based implementations can be overridden.

For -all implementations using the version 2 resource file format, therom_only member -must be set explicitly. - - + + + + + +Preventing +Plug-in Overriding The plug-in framework supports two methods to prevent a RAM based +plug-in from overriding a ROM based plug-in. The first method is to use the +ROM-only resolver and the second method is to explicitly prevent a ROM-based +implementation from being overridden by a RAM-based implementation. +

Using the ROM-only +resolver restricts the search of the framework plug-ins to the ROM only.

Alternatively, +to prevent a RAM-based implementation from overriding a ROM-based implementation, +set the rom_only variable to 1 in the resource +registration file for the implementation.

+ +Using the ROM-only resolver +

Use KRomOnlyResolverUid as the CResolver +UID passed to those variants of REComSession::ListImplementationsL() and REComSession::CreateImplementationL() that take the TUid aResolverUid parameter.

If an +installable upgrade to a ROM-based plug-in is correctly supplied by a vendor, +then the ROM-only resolver finds and uses the upgrade. Platform security controls +are used to ensure that the upgrade is secure. For details, see How to upgrade +ROM-based plug-ins securely.

+ +Preventing a ROM-based implementation from being overridden: +

If the ROM-based plug-ins must be prevented from being overridden +by a RAM-based plug-in, use the version +2 resource file format.

In the .rss file, +the rom_only member of the IMPLEMENTATION_INFO structure +must be set to 1.

rom_only set to 1 indicates the +ROM-based implementation must be used.

rom_only set +to 0 indicates the ROM-based implementations can be overridden.

For +all implementations using the version 2 resource file format, therom_only member +must be set explicitly. + + \ No newline at end of file