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 task

    11   PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd">

    12 <task id="GUID-3B0602F1-4294-43C4-9E7A-B1A33291C22F" xml:lang="en"><title>Establishing

    13 a connection with destination networks</title><shortdesc>Destination networks, also known as Service Network Access Points

    14 (SNAPs) avoid the connectivity problems that are related to the access point

    15 being fixed for the duration of the data connection.  With the availability

    16 of WLAN and other data bearers, the number of access points has grown considerably.

    17  With WLAN, the availability of an access point can change frequently.  A

    18 fixed access point in selection often leads to a poor access point choice.

    19 Because the network environment is now more dynamic, you can have either a

    20 safe but slow connection, or a fast but unreliable connection. In practice

    21 this means that the application is either stuck with using GPRS or the user

    22 must continuously change the settings to point to the WLAN access point that

    23 happens to be available.  A fixed access point leads to non-optimal usage

    24 of available connections, especially with applications that use long-lasting

    25 data connections.</shortdesc><prolog><metadata><keywords/></metadata></prolog><taskbody>

    26 <prereq id="GUID-9A30000D-83AF-40B7-B0DD-E9AFFD1B7019">       <p>Applications

    27 should monitor the connection state by using platform services (such as Connection

    28 Monitor Server API) and avoid polling and keep-alives. If the application

    29 protocol mandates the use of timers, they should be tuned so that the control

    30 data over the air is minimized. </p>     </prereq>

    31 <steps id="GUID-4DD07DEC-6017-4237-BE46-1D69E5FBD744-GENID-1-10-1-14-1-1-7-1-3-2">

    32 <step id="GUID-9A69E5AD-E938-4092-A8C2-CB65C37C8962-GENID-1-10-1-14-1-1-7-1-3-2-1"><cmd><xref href="GUID-E2E2FACF-5D4F-43E8-8B53-B268252CF572.dita">Defining

    33 Connection Management Items</xref></cmd>

    34 </step>

    35 <step id="GUID-725900FE-86E4-4A8F-A896-1F1661B4C1BB"><cmd><xref href="GUID-A2F691C8-9525-4028-BF82-70E9D50630C6.dita">Prompting

    36 the user to select a destination network</xref></cmd>

    37 </step>

    38 <step id="GUID-96317261-F1CC-423C-815E-70CD4F0A3AD7"><cmd><xref href="GUID-DBF6760F-D209-4B8F-89D5-A7EFFF7959E2.dita">Starting

    39 the Connection through the Destination Network</xref></cmd>

    40 </step>

    41 </steps>

    42 </taskbody></task>