QNAM Doc: Remove mention of bearer

🐻er management is going away

Change-Id: I86067d593ece0d35a33f23130260ccb7c4b64881
Reviewed-by: Timur Pocheptsov <timur.pocheptsov@qt.io>

src/network/access/qnetworkaccessmanager.cpp

@@ -220,27 +220,6 @@ static void ensureInitialized()
     can be:
     \snippet code/src_network_access_qnetworkaccessmanager.cpp 1
 
-    \section1 Network and Roaming Support
-
-    With the addition of the \l {Bearer Management} API to Qt 4.7
-    QNetworkAccessManager gained the ability to manage network connections.
-    QNetworkAccessManager can start the network interface if the device is
-    offline and terminates the interface if the current process is the last
-    one to use the uplink. Note that some platforms utilize grace periods from
-    when the last application stops using a uplink until the system actually
-    terminates the connectivity link. Roaming is equally transparent. Any
-    queued/pending network requests are automatically transferred to the new
-    access point.
-
-    Clients wanting to utilize this feature should not require any changes. In fact
-    it is likely that existing platform specific connection code can simply be
-    removed from the application.
-
-    \note The network and roaming support in QNetworkAccessManager is conditional
-    upon the platform supporting connection management. The
-    \l QNetworkConfigurationManager::NetworkSessionRequired can be used to
-    detect whether QNetworkAccessManager utilizes this feature.
-
     \sa QNetworkRequest, QNetworkReply, QNetworkProxy
 */
 

src/network/doc/src/network-programming.qdoc

@@ -261,29 +261,4 @@
     by passing a factory to QNetworkProxyFactory::setApplicationProxyFactory()
     and a custom proxying policy can be created by subclassing
     QNetworkProxyFactory; see the class documentation for details.
-
-    \section1 Bearer Management Support
-
-    Bearer Management controls the connectivity state of the device such that
-    the application can start or stop network interfaces and roam
-    transparently between access points.
-
-    The QNetworkConfigurationManager class manages the list of network
-    configurations known to the device. A network configuration describes the
-    set of parameters used to start a network interface and is represented by
-    the QNetworkConfiguration class.
-
-    A network interface is started by openning a QNetworkSession based on a
-    given network configuration. In most situations creating a network session
-    based on the platform specified default network configuration is
-    appropriate. The default network configuration is returned by the
-    QNetworkConfigurationManager::defaultConfiguration() function.
-
-    On some platforms it is a platform requirement that the application open a
-    network session before any network operations can be performed. This can be
-    tested by the presents of the
-    QNetworkConfigurationManager::NetworkSessionRequired flag in the value
-    returned by the QNetworkConfigurationManager::capabilities() function.
-
-    \sa {Bearer Management}
 */

src/network/doc/src/qtnetwork.qdoc

@@ -54,7 +54,6 @@
     applications with networking capabilities.
     \list
     \li \l{Network Programming with Qt} - Programming applications with networking capabilities
-    \li \l{Bearer Management} - An API to control the system's connectivity state
     \li \l{Secure Sockets Layer (SSL) Classes} - Classes for secure communication over network sockets
     \endlist