andagindfor pcn by WP The matching occurs before any WAP Push handler is invoked. If a WAP F 3.3.2 White/Black List URI Service of URI specified in IETF RFC 3986. Reso pem ons retu are or un k UR The hich ReadDeviceData capability. ASsqeLURaeededobeupeadeaynoegeneaApenatre dati 3.4 RAM Defragmentation areas Note that there is no direct user-side API to invoke RAM defragmentation. Further details can be found in 2.2 above 4 Conclusion Further information on these changes will be available initially in the Migration Guides in the Symbian OS Developer Library which comes with the DevKit. Want to be kept informed of new articles being made available on the Symbian Developer Network? Subscribe to the Symbian Community Newsletter. Community Newsletter brings you.every month,the latest news and resourcs developer.symbian.com symbian5 discarding blacklisted messages and flagging whitelisted messages for processing by the WAP Push Handler. The matching occurs before any WAP Push handler is invoked. If a WAP Push message matches a black list entry, the WAP Push message is silently discarded by the WAP Push component. Otherwise, the WAP Push message is flagged as to whether or not it matched a white list entry and then dispatched to the WAP Push handler. 3.3.2 White/Black List URI Service To support WAP Push white and black lists, Symbian OS provides a new service for querying and updating a list of URIs and associated remote access permissions. The URI syntax supported is as specified in IETF RFC 3986. The URI syntax covers both URLs (Uniform Resource Locators, for example HTTP addresses) and URNs (Uniform Resource Names, for example OIDs). IETF guidance is that specifications previously referencing URLs should now refer to URIs (see RFC 3305). The service provides an API which can be used to query the permission associated with a specified URI (possible permissions returned are ‘allowed’, ‘denied’, or ‘unknown’). The API includes a parameter indicating the purpose of the query, so as to disambiguate similar URIs which may have been included in the list for different purposes. This query API is protected with ReadDeviceData capability. The APIs for updating the URI list are expected to be superceded by more general APIs in a future security settings service. 3.4 RAM Defragmentation To complement memory usage improvements in Symbian OS v9.4, a Defragment RAM API has been added to the kernel. When called, it defragments specified areas of RAM as much as possible and report on current memory usage. Note that there is no direct user-side API to invoke RAM defragmentation. Further details can be found in 2.2 above. 4 Conclusion A brief summary of the key features and technical specifications of Symbian OS v9.4 can be found on the Symbian web site in the Symbian OS Releases information page. Further information on these changes will be available initially in the Migration Guides in the Symbian OS Developer Library which comes with the DevKit. Want to be kept informed of new articles being made available on the Symbian Developer Network? Subscribe to the Symbian Community Newsletter. The Symbian Community Newsletter brings you, every month, the latest news and resources for Symbian OS