diff -r 48780e181b38 -r 578be2adaf3e Symbian3/PDK/Source/GUID-EAD6B365-DCB9-51AD-AF21-0B8262B468A2.dita --- a/Symbian3/PDK/Source/GUID-EAD6B365-DCB9-51AD-AF21-0B8262B468A2.dita Tue Jul 20 12:00:49 2010 +0100 +++ b/Symbian3/PDK/Source/GUID-EAD6B365-DCB9-51AD-AF21-0B8262B468A2.dita Fri Aug 13 16:47:46 2010 +0100 @@ -1,38 +1,38 @@ - - - - - -WhiteList/BlackList -URI Services Overview -

Mobile widgets are increasingly being used to connect to internet, which -has increased the vulnerability of devices. To address this issue, Symbian -provides a framework using which origins of harmful messages can be added -to a BlackList. The framework also supports adding the origin of trusted clients -to a WhiteList. This allows end users to control the data they receive from -networks.

-

Symbian provides a client-server framework to support BlackList/WhiteList -origins (URIs). The framework currently supports Browser, WapPush, PushEmail and DeviceProvisioning service -type URIs. The URI entry is unique for a given service type and similar URIs -from different service types can exist in the URI list.

-

The BlackList/WhiteList framework provides support for adding a URI to -the list, removing a URI from list, updating a URI in the list, reading URIs -from the list, and querying for URIs in the list. Support for wildcard URI -entries is not provided. The framework also provides support for pre-configuration -of URIs in the list to enable clients to add their own URIs.

-

See Also

- + + + + + +WhiteList/BlackList +URI Services Overview +

Mobile widgets are increasingly being used to connect to internet, which +has increased the vulnerability of devices. To address this issue, Symbian +provides a framework using which origins of harmful messages can be added +to a BlackList. The framework also supports adding the origin of trusted clients +to a WhiteList. This allows end users to control the data they receive from +networks.

+

Symbian provides a client-server framework to support BlackList/WhiteList +origins (URIs). The framework currently supports Browser, WapPush, PushEmail and DeviceProvisioning service +type URIs. The URI entry is unique for a given service type and similar URIs +from different service types can exist in the URI list.

+

The BlackList/WhiteList framework provides support for adding a URI to +the list, removing a URI from list, updating a URI in the list, reading URIs +from the list, and querying for URIs in the list. Support for wildcard URI +entries is not provided. The framework also provides support for pre-configuration +of URIs in the list to enable clients to add their own URIs.

+

See Also

+
    +
  • Using +URIs from the URI List

  • +
  • Querying +URIs from the URI List

  • +
  • Pre-configuring +the URI List

  • +
\ No newline at end of file