Documentation/Maemo 5 Developer Guide/Architecture/Connectivity - Revision history

imported_>amigadave: multimedia domain link

2010-10-20T12:21:49Z

multimedia domain link

← Older revision		Revision as of 12:21, 20 October 2010
Line 7:		Line 7:
	Wireless Internet connectivity is supported for IPv4 over WLAN networks. IPv4 address configuration is done using DHCP or static addresses.		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].		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].

	====Lower level implementation details====		====Lower level implementation details====
Line 15:		Line 15:
	===Local connectivity===		===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:		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:

	* 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.		* 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===

	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.		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.

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

imported_>amigadave: wikify slightly

2010-07-19T11:00:04Z

wikify slightly

← Older revision		Revision as of 11:00, 19 July 2010
Line 1:		Line 1:
	~~=Connectivity domain=~~
	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.		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.

Line 5:		Line 4:

	===Internet connectivity===		===Internet connectivity===

	Wireless Internet connectivity is supported for IPv4 over WLAN networks. IPv4 address configuration is done using DHCP or static addresses.		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].		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====

	~~'''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.

	~~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/ DBus APIs provided osso-wlan]. If you wish to only the scan the network interfaces, then ICd2 is sufficient.		===Local connectivity===

	~~===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:		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:

Line 22:		Line 22:

	===Home connectivity===		===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.		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.

Line 27:		Line 28:

	===User Interface===		===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.		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.

imported_>amigadave: catgeorise

2010-02-12T12:01:45Z

catgeorise

← Older revision		Revision as of 12:01, 12 February 2010
Line 28:		Line 28:
	===User Interface===		===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.		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]]

imported_>tapio at 10:25, 12 February 2010

2010-02-12T10:25:59Z

← Older revision		Revision as of 10:25, 12 February 2010
Line 12:		Line 12:
	'''Lower level implementation details'''		'''Lower level implementation details'''

	Experienced developers can extend internet connectivity by adding new network interfaces using [http://maemo.org/api_refs/5.0/~~beta~~/icd2/ ICd2] APIs. They can also control the WLAN interfaces using the [http://maemo.org/api_refs/5.0/~~beta~~/~~osso_wlan~~/ DBus APIs provided osso-wlan]. If you wish to only the scan the network interfaces, then ICd2 is sufficient.		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/ DBus APIs provided osso-wlan]. If you wish to only the scan the network interfaces, then ICd2 is sufficient.

	===Local connectivity===		===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/~~beta~~/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/~~beta~~/osso-gwobex/gw-obex_8h.html libgwobex] API reference for more details.		* 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.		* 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.		* Support for BT mono and stereo headsets via BT HSP, BT HFP and A2DP protocols.

imported_>tapio at 10:22, 12 February 2010

2010-02-12T10:22:56Z

← Older revision		Revision as of 10:22, 12 February 2010
Line 7:		Line 7:
	Wireless Internet connectivity is supported for IPv4 over WLAN networks. IPv4 address configuration is done using DHCP or static addresses.		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/~~beta~~/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].

imported_>bijjal: New page: =Connectivity domain= The Connectivity domain provides the APIs, user interfaces, and underlying user-space and kernel components for Wireless Internet connectivity, wireless local connect...

2009-08-31T11:28:33Z

New page: =Connectivity domain= The Connectivity domain provides the APIs, user interfaces, and underlying user-space and kernel components for Wireless Internet connectivity, wireless local connect...

New page

=Connectivity domain=
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/beta/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/beta/icd2/ ICd2] APIs. They can also control the WLAN interfaces using the [http://maemo.org/api_refs/5.0/beta/osso_wlan/ DBus 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/beta/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/beta/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.