Editing Documentation/Maemo 5 Developer Guide/Architecture/Connectivity

Warning: You are not logged in. Your IP address will be recorded in this page's edit history.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.

Learn more about Contributing to the wiki.

The Connectivity domain provides the APIs, user interfaces, and underlying user-space and kernel components for Wireless Internet connectivity, wireless local connectivity and Home connectivity.

==Functionality provided==

===Internet connectivity===

Wireless Internet connectivity is supported for IPv4 over WLAN networks. IPv4 address configuration is done using DHCP or static addresses.

Internet Connectivity Daemon (ICd2) handles network connectivity in the Device. Applications should use the shared libconic library API to request connectivity instead of directly interacting with ICd2. Refer the API documentation for [http://maemo.org/api_refs/5.0/5.0-final/libconic/index.html libconic].

====Lower level implementation details====

Experienced developers can extend internet connectivity by adding new network interfaces using [http://maemo.org/api_refs/5.0/5.0-final/icd2/ ICd2] APIs. They can also control the WLAN interfaces using the [http://maemo.org/api_refs/5.0/5.0-final/osso-wlan/ D-Bus APIs provided osso-wlan]. If you wish to only the scan the network interfaces, then ICd2 is sufficient.

===Local connectivity===

The Wireless local connectivity consists of Bluetooth connectivity. [http://www.bluez.org/about/ Bluez] provides the bluetooth protocol stack. Refer the [http://maemo.org/api_refs/5.0/5.0-final/bluez/ API documentation] for its usage. It supports the following features:

* Data exchange between devices using BT OPP. Refer [http://maemo.org/api_refs/5.0/5.0-final/osso-gwobex/gw-obex_8h.html libgwobex] API reference for more details.
* Access the filesystem of the Rover device using BT FTP protocol. 
* Support for BT mono and stereo headsets via BT HSP, BT HFP and A2DP protocols.

===Home connectivity===

Home connectivity consists of a UPnP stack with Internet Gateway Device (IGD) and Audio Video (AV) support. GUPnP stack supported by Multimedia domain should be used for any new application development.

The old clinkc UPnP stack provided by Connectivity domain still exists due to legacy reasons and is deprecated.

===User Interface===

The Connectivity domain also includes UI components related to Connectivity. These include the connectivity related status bar indicators, dialogs, applications, wizards, and control panel applets.

[[Category:Development]]
[[Category:Documentation]]
[[Category:Fremantle]]

Please note that all contributions to maemo.org wiki may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see maemo.org wiki:Copyrights for details). Do not submit copyrighted work without permission!

Summary:

Cancel | Editing help (opens in new window)

Retrieved from "http://wiki.maemo.org/Documentation/Maemo_5_Developer_Guide/Architecture/Connectivity"

Personal tools

Navigation

Views

Editing Documentation/Maemo 5 Developer Guide/Architecture/Connectivity

@@ Line 7: / Line 7: @@
 Wireless Internet connectivity is supported for IPv4 over WLAN networks. IPv4 address configuration is done using DHCP or static addresses.
-Internet Connectivity Daemon (ICd2) handles network connectivity in the Device. Applications should use the shared libconic library API to request connectivity instead of directly interacting with ICd2. Refer tothe API documentation for [http://maemo.org/api_refs/5.0/5.0-final/libconic/index.html libconic].
+Internet Connectivity Daemon (ICd2) handles network connectivity in the Device. Applications should use the shared libconic library API to request connectivity instead of directly interacting with ICd2. Refer the API documentation for [http://maemo.org/api_refs/5.0/5.0-final/libconic/index.html libconic].
 ====Lower level implementation details====
@@ Line 15: / Line 15: @@
 ===Local connectivity===
-The Wireless local connectivity consists of Bluetooth connectivity. [http://www.bluez.org/about/ Bluez] provides the Bluetooth protocol stack. Refer to the [http://maemo.org/api_refs/5.0/5.0-final/bluez/ API documentation] for its usage. It supports the following features:
+The Wireless local connectivity consists of Bluetooth connectivity. [http://www.bluez.org/about/ Bluez] provides the bluetooth protocol stack. Refer the [http://maemo.org/api_refs/5.0/5.0-final/bluez/ API documentation] for its usage. It supports the following features:
 * Data exchange between devices using BT OPP. Refer [http://maemo.org/api_refs/5.0/5.0-final/osso-gwobex/gw-obex_8h.html libgwobex] API reference for more details.
@@ Line 23: / Line 23: @@
 ===Home connectivity===
-Home connectivity consists of a UPnP stack with Internet Gateway Device (IGD) and Audio Video (AV) support. GUPnP stack supported by [[Documentation/Maemo 5 Developer Guide/Architecture/Multimedia Domain|Multimedia domain]] should be used for any new application development.
+Home connectivity consists of a UPnP stack with Internet Gateway Device (IGD) and Audio Video (AV) support. GUPnP stack supported by Multimedia domain should be used for any new application development.
 The old clinkc UPnP stack provided by Connectivity domain still exists due to legacy reasons and is deprecated.