Symbian3/PDK/Source/GUID-51FB640F-AD0E-5A1A-80C3-D7AA53B31A21.dita
changeset 1 25a17d01db0c
child 3 46218c8b8afa
equal deleted inserted replaced
0:89d6a7a84779 1:25a17d01db0c
       
     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-51FB640F-AD0E-5A1A-80C3-D7AA53B31A21" xml:lang="en"><title>Comms
       
    13 User Prompt Service</title><shortdesc> The Comms User Prompt Service (UPS) enables even unsigned applications
       
    14 to access the network if user authorisation is provided. </shortdesc><prolog><metadata><keywords/></metadata></prolog><conbody>
       
    15 <p>According to the platform model of Symbian platform any application connecting
       
    16 to a network must have the <codeph>NetworkServices</codeph> capability. All
       
    17 applications that have the <codeph>Networking service</codeph> capability
       
    18 must be signed .</p>
       
    19 <p>The target audience of this document are the licensees who write <xref href="GUID-F43A54C0-E82B-5790-8493-1372D214C642.dita#GUID-F43A54C0-E82B-5790-8493-1372D214C642/GUID-2372FF88-FA59-5CDF-9362-1A54F43D8442">MCPR</xref> plug-ins.
       
    20 Symbian provides a <xref href="GUID-7BDC5FC0-15AD-56D3-BB64-C35F0C34A31F.dita">reference</xref> plug-in
       
    21 for the licensees, which can be modified for customisation. The licensees
       
    22 implementing the comms user prompt service must have knowledge of the Comms
       
    23 Framework, for more information see <xref href="GUID-8F2D6AC8-8357-55C7-970B-CD2684BA9B04.dita">Communications
       
    24 Framework</xref>. </p>
       
    25 <section><title>User Prompt Service (UPS)</title> <p>Any application that
       
    26 requires network access uses the <xref href="GUID-61E0CD76-A2E3-5066-84A8-146EECA8ADCD.dita">Socket
       
    27 Server</xref> API using <xref href="GUID-BED8A733-2ED7-31AD-A911-C1F4707C67FD.dita"><apiname>RConnection</apiname></xref> or <xref href="GUID-D4F08503-F1EF-3531-9C3C-4AF24A6255F0.dita"><apiname>RSocket</apiname></xref>.
       
    28 The platform security model checks the capability of the client application
       
    29 to access the network. The comms user prompt service is used to notify the
       
    30 user about the network access. The UPS feature enables applications without <codeph>NetworkServices</codeph> capability
       
    31 to access the network if the user authorises the connection. </p> </section>
       
    32 <section><title> User Prompt</title> <p>When comms UPS is implemented, the
       
    33 user is requested to authorise a network connection, when an application opens
       
    34 a new connection or when it attaches to an existing connection. The UPS prompts
       
    35 the user when an application tries to send data through a socket which is
       
    36 not explicitly associated with an authorised network connection. The IP network
       
    37 user prompt is implemented as an MCPR plug-in. The plug-in will invoke the
       
    38 UPS server. The UPS functionality can be <xref href="GUID-81238E98-755C-5E86-ADEA-6A675E058289.dita">configured</xref> by
       
    39 the developers. </p> </section>
       
    40 <section><title>Network Life Time</title> <p>When the comms user prompt service
       
    41 component is configured for Network session life time, user responds to a
       
    42 UPS dialog prompt by authorising the request with either '<codeph>Session
       
    43 Yes</codeph>' or '<codeph>Always</codeph>' response. Any other applications
       
    44 running in the same process of the user authorised application will be granted
       
    45 the network access. The UPS response for a particular process is valid for
       
    46 the duration of the network connection associated with the process. </p> </section>
       
    47 <section><title>Session Life Time</title> <p>When the comms user prompt service
       
    48 component is configured for Session life time, user responds to a UPS dialog
       
    49 prompt by authorising the request with either '<codeph>Session Yes</codeph>'
       
    50 or '<codeph>Always</codeph>' response. Any other applications running in the
       
    51 same process of the user authorised session will be granted network access
       
    52 for the duration of the process. </p> </section>
       
    53 <section><title>User Prompt Service Server</title> <p>The UPS server generates
       
    54 the user prompts and responds back to the MCPR with the user selection. The
       
    55 dialog creator, a UPS plug-in, formats and streams the dialog box to the UPS
       
    56 server. The UPS server interacts with the User Interface (UI) and responds
       
    57 back to the MCPR. </p> <p>The UPS server is also responsible for checking
       
    58 the policy files which has the details of the process and the available options. </p> </section>
       
    59 </conbody></concept>