Archived:Capability requirements for Flash Lite Viewer API
hamishwillee
(Talk | contribs) m (Hamishwillee - Bot change of template (Template:KnowledgeBase) - now using Template:ArticleMetaData) |
debjit.roy
(Talk | contribs) (Debjit.roy -) |
||
| Line 1: | Line 1: | ||
| + | [[Category:Technical Solution]][[Category:Symbian C++]][[Category:Flash Lite]][[Category:S60 3rd Edition, Feature Pack 1]] | ||
__NOTOC__ | __NOTOC__ | ||
__NOEDITSECTION__ | __NOEDITSECTION__ | ||
| Line 20: | Line 21: | ||
}} | }} | ||
| + | {{Archived|timestamp=20120314043953|user=roy.debjit| }} | ||
== Overview == | == Overview == | ||
Capability requirements for Flash Lite Viewer API | Capability requirements for Flash Lite Viewer API | ||
| Line 25: | Line 27: | ||
== Description == | == Description == | ||
According to the S60 3rd Edition FP1 SDK, the new Flash Lite Viewer API requires that the stub application using it has NetworkControl capability. This implies that every standalone Flash application has to be Symbian Signed.<br>The information provided in the API documentation is incorrect, NetworkControl is not an unconditional capability requirement.<br>The purpose of the API is to provide a flexible mechanism for Flash Lite applications to be presented to the user in the phone<nowiki>’</nowiki>s application list (menu) with a customized icon and with its own platform security context. This is done by creating a basic Symbian OS application skeleton whose document would in fact be an instance of the Flash Light engine rendering a specified Flash animation (that can be for security reason installed in the application<nowiki>’</nowiki>s own data cage). With regards to the Platform Security context the application will have its own SecureID, VendorID, and a capability set designed to fit the requirements of the Flash application. That means that if, for example, the only capability-controlled functionality that the Flash application implements is Internet access, then declaring the NetworkServices capability for the stub Symbian OS application would be enough to satisfy the security policies. In this scenario submitting your application for certification is recommended but not mandatory. | According to the S60 3rd Edition FP1 SDK, the new Flash Lite Viewer API requires that the stub application using it has NetworkControl capability. This implies that every standalone Flash application has to be Symbian Signed.<br>The information provided in the API documentation is incorrect, NetworkControl is not an unconditional capability requirement.<br>The purpose of the API is to provide a flexible mechanism for Flash Lite applications to be presented to the user in the phone<nowiki>’</nowiki>s application list (menu) with a customized icon and with its own platform security context. This is done by creating a basic Symbian OS application skeleton whose document would in fact be an instance of the Flash Light engine rendering a specified Flash animation (that can be for security reason installed in the application<nowiki>’</nowiki>s own data cage). With regards to the Platform Security context the application will have its own SecureID, VendorID, and a capability set designed to fit the requirements of the Flash application. That means that if, for example, the only capability-controlled functionality that the Flash application implements is Internet access, then declaring the NetworkServices capability for the stub Symbian OS application would be enough to satisfy the security policies. In this scenario submitting your application for certification is recommended but not mandatory. | ||
| − | |||
| − | |||
Revision as of 07:39, 14 March 2012
Article Metadata
Compatibility
Article
Overview
Capability requirements for Flash Lite Viewer API
Description
According to the S60 3rd Edition FP1 SDK, the new Flash Lite Viewer API requires that the stub application using it has NetworkControl capability. This implies that every standalone Flash application has to be Symbian Signed.
The information provided in the API documentation is incorrect, NetworkControl is not an unconditional capability requirement.
The purpose of the API is to provide a flexible mechanism for Flash Lite applications to be presented to the user in the phone’s application list (menu) with a customized icon and with its own platform security context. This is done by creating a basic Symbian OS application skeleton whose document would in fact be an instance of the Flash Light engine rendering a specified Flash animation (that can be for security reason installed in the application’s own data cage). With regards to the Platform Security context the application will have its own SecureID, VendorID, and a capability set designed to fit the requirements of the Flash application. That means that if, for example, the only capability-controlled functionality that the Flash application implements is Internet access, then declaring the NetworkServices capability for the stub Symbian OS application would be enough to satisfy the security policies. In this scenario submitting your application for certification is recommended but not mandatory.
