Documentation/Maemo 5 Developer Guide/Using Connectivity Components/Maemo Connectivity - Revision history

imported_>amigadave: /* Connectivity Subsystem */ convert tables to definition lists

2011-03-01T13:56:18Z

Connectivity Subsystem: convert tables to definition lists

← Older revision		Revision as of 13:56, 1 March 2011
Line 24:		Line 24:
	In offline mode, none of the radios must be active. The [[Documentation/Maemo 5 Developer Guide/Architecture/System Software#Device State Management Entity (DSME)\|Device System Management Entity (DSME)]] of Maemo provides information about the transitions to and from the offline mode.		In offline mode, none of the radios must be active. The [[Documentation/Maemo 5 Developer Guide/Architecture/System Software#Device State Management Entity (DSME)\|Device System Management Entity (DSME)]] of Maemo provides information about the transitions to and from the offline mode.

	~~{\| class="wikitable"~~		;Name
	! Name		: Connectivity UI
	! Connectivity UI		;Purpose
	\|-		: Provides the UI for managing phone and Internet connections. Available as a Control Panel applet, and from the Status Bar.
	\| Purpose		;Responsibilities and additional requirements
	\| Provides the UI for managing phone and Internet connections. Available as a Control Panel applet, and from the Status Bar.		: <ul><li>Displaying active connections with statistics</li><li>Updating status indicators</li><li>Providing dialogs for changing and disconnecting connections</li></ul>
	\|-		;Concurrent usage
	\| Responsibilities and additional requirements		: (N/A)
	\|
	* Displaying active connections with statistics
	* Updating status indicators
	* Providing dialogs for changing and disconnecting connections
	\|-
	\| Concurrent usage
	\| (N/A)
	\|}

	~~{\| class="wikitable"~~		;Name
	! Name		: Phone Access
	! Phone Access		;Purpose
	\|-		: Provides connections to phones with different Bluetooth profiles
	\| Purpose		;Responsibilities and additional requirements
	\| Provides connections to phones with different Bluetooth profiles		: <ul><li>Searching for phones and inquiring their services</li><li>Keeping phone register</li><li>Providing status of the phone connections for Connectivity UI</li><li>Binding RFCOMM devices to Bluetooth services on the phone</li><li>Providing easy access to OpenOBEX</li></ul>
	\|-		;Concurrent usage
	\| Responsibilities and additional requirements		: Number of clients not limited by Maemo. However, some phones may not support more than one Bluetooth profile at a time.
	\|
	* Searching for phones and inquiring their services
	* Keeping phone register
	* Providing status of the phone connections for Connectivity UI
	* Binding RFCOMM devices to Bluetooth services on the phone
	* Providing easy access to OpenOBEX
	\|-
	\| Concurrent usage
	\| Number of clients not limited by Maemo. However, some phones may not support more than one Bluetooth profile at a time.
	\|}

	~~{\| class="wikitable"~~		;Name
	! Name		: Internet Access
	! Internet Access		;Purpose
	\|-		: Provides Internet connections over different bearers.
	\| Purpose		;Responsibilities and additional requirements
	\| Provides Internet connections over different bearers.		: <ul><li>Providing means for configuration and management of IAP settings</li><li>Providing API for Internet connections over different bearers (e.g. WLAN, GPRS)</li><li>Providing status of Internet connections for Connectivity UI</li></ul>
	\|-		;Concurrent usage
	\| Responsibilities and additional requirements		: Number of clients not limited, but only one connection to the Internet can exist at any given time
	\|
	* Providing means for configuration and management of IAP settings
	* Providing API for Internet connections over different bearers (e.g. WLAN, GPRS)
	* Providing status of Internet connections for Connectivity UI
	\|-
	\| Concurrent usage
	\| Number of clients not limited, but only one connection to the Internet can exist at any given time
	\|}

	Phone and Internet connections are quite different by nature and behavior. These are introduced in more detail in the following sections.		Phone and Internet connections are quite different by nature and behavior. These are introduced in more detail in the following sections.

imported_>dneary: /* Libconic Usage */

2010-09-13T18:18:33Z

Libconic Usage

← Older revision		Revision as of 18:18, 13 September 2010
Line 267:		Line 267:
	==== Requesting for Connection ====		==== Requesting for Connection ====

	~~Libconic~~ is an asynchronous connection API, which heavily relies on <code>GObject</code> signals. Basically this means that <code>GMainloop</code> must be iterated in order to successfully execute connection requests. After the application is set up, use a <code>ConIcConnection</code> object to request a connection:		[http://maemo.org/api_refs/5.0/5.0-final/libconic/ LibConIc] is an asynchronous connection API, which heavily relies on <code>GObject</code> signals. Basically this means that <code>GMainloop</code> must be iterated in order to successfully execute connection requests. After the application is set up, use a <code>ConIcConnection</code> object to request a connection:

	<source lang="c">		<source lang="c">
Line 281:		Line 281:
	</source>		</source>

	At this point, the application does not yet have an Internet connection. A successful return from <code>con_ic_connection_connect()</code> means only that the request was successfully dispatched to the Internet Connectivity daemon. When the daemon has a connection ready, the application receives an event (as an <code>GObject</code> signal) indicating that the device is connected. If the connection attempt fails, the application receives a disconnected event with an error describing the reason for the failure.		At this point, the application does not yet have an Internet connection. A successful return from <code>con_ic_connection_connect()</code> means only that the request was successfully dispatched to the Internet Connectivity daemon. When the daemon has a connection ready, the application receives an [http://maemo.org/api_refs/5.0/5.0-final/libconic/conicconnectionevent_8h.html event] (as an <code>GObject</code> signal) indicating that the device is connected. If the connection attempt fails, the application receives a disconnected event with an error describing the reason for the failure.

	The connection handler (<code>my_connection_handler()</code> function registered in the previous snippet) could look like this:		The connection handler (<code>my_connection_handler()</code> function registered in the previous snippet) could look like this:

imported_>amigadave: /* Connectivity Subsystem */ add DSME link

2010-09-08T08:52:54Z

Connectivity Subsystem: add DSME link

← Older revision		Revision as of 08:52, 8 September 2010
Line 22:		Line 22:
	This section describes the system decomposition of the Connectivity subsystem. Maemo applications can open Internet connections by using the LibConIC API. The Internet Access subsystem take care of the connection to the phone, if necessary, by using the services of the Phone Access subsystem. If an application needs to gain access to the phone's files, the File selector consults the Phone Access subsystem.		This section describes the system decomposition of the Connectivity subsystem. Maemo applications can open Internet connections by using the LibConIC API. The Internet Access subsystem take care of the connection to the phone, if necessary, by using the services of the Phone Access subsystem. If an application needs to gain access to the phone's files, the File selector consults the Phone Access subsystem.

	In offline mode, none of the radios must be active. The Device System Management Entity (DSME) of Maemo provides information about the transitions to and from the offline mode.		In offline mode, none of the radios must be active. The [[Documentation/Maemo 5 Developer Guide/Architecture/System Software#Device State Management Entity (DSME)\|Device System Management Entity (DSME)]] of Maemo provides information about the transitions to and from the offline mode.

	{\| class="wikitable"		{\| class="wikitable"

imported_>amigadave: close list

2010-09-08T08:29:32Z

close list

← Older revision		Revision as of 08:29, 8 September 2010
Line 139:		Line 139:
	: IC daemon establishes Internet connections over different bearers.		: IC daemon establishes Internet connections over different bearers.
	;Responsibilities and additional requirements		;Responsibilities and additional requirements
	: <ul><li>Controlling that only one Internet connection (one active IAP) can exist at any given time</li><li>Using WLAN or GPRS connection daemon for getting a network device and getting the connection authenticated</li><li>Starting IP level services like PPP and DHCP</li><li>Providing statistics about the usage of IAPs to any application</li>		: <ul><li>Controlling that only one Internet connection (one active IAP) can exist at any given time</li><li>Using WLAN or GPRS connection daemon for getting a network device and getting the connection authenticated</li><li>Starting IP level services like PPP and DHCP</li><li>Providing statistics about the usage of IAPs to any application</li></ul>
	;Concurrent usage		;Concurrent usage
	: Has multiple clients and limits the connections to one at a time		: Has multiple clients and limits the connections to one at a time

imported_>amigadave: /* Discovering devices */ minor tidy

2010-08-30T08:40:32Z

Discovering devices: minor tidy

← Older revision		Revision as of 08:40, 30 August 2010
Line 536:		Line 536:
	=== Discovering devices ===		=== Discovering devices ===

	Maemo provides D-~~BUS~~ interface for displaying ~~bluetooth~~ device search dialog (You can find list of available Bluetooth D-~~BUS~~ calls [[#D-Bus Connectivity UI Interface\|~~here~~]]).		Maemo provides a D-Bus interface for displaying a Bluetooth device search dialog (You can find a list of available Bluetooth D-Bus calls [[#D-Bus Connectivity UI Interface\|below]]).

	Devices can be searched with following steps:		Devices can be searched with following steps:
	# Set up D-~~BUS~~ connection		# Set up a D-Bus connection
	# call bt_ui.search_req to show dialog - you can filter the results		# call <code>bt_ui.search_req</code> to show the dialog - you can filter the results
	# catch bt_ui.search_result signal		# catch <code>bt_ui.search_result</code> signal
	# process results		# process the results

			Here is a working example in C:
	Here's working example in C ~~how this is done~~:

	<source lang="c">		<source lang="c">
	//Bluetooth discovery example - bluetooth libraries ~~won't~~ work in SDK!		// Bluetooth discovery example - bluetooth libraries will not work in the SDK!
	#include <hildon/hildon-program.h>		#include <hildon/hildon-program.h>
	#include <dbus/dbus.h>		#include <dbus/dbus.h>

imported_>durazell: /* Discovering devices */

2010-08-27T20:57:06Z

Discovering devices

← Older revision		Revision as of 20:57, 27 August 2010
Line 548:		Line 548:

	<source lang="c">		<source lang="c">
	//Bluetooth discovery example		//Bluetooth discovery example - bluetooth libraries won't work in SDK!
	#include <hildon/hildon-program.h>		#include <hildon/hildon-program.h>
	#include <dbus/dbus.h>		#include <dbus/dbus.h>

imported_>durazell: /* Bluetooth Libraries */

2010-08-27T20:55:04Z

Bluetooth Libraries

Show changes

imported_>amigadave: use `, tidy`


2010-08-17T12:43:47Z
use <code>, tidy
Show changes



imported_>amigadave: /* Bluetooth DBUS UI dialogs */ use 
2010-08-04T09:54:47Z
Bluetooth DBUS UI dialogs:  use <source>
Show changes


imported_>amigadave: /* D-Bus Connectivity UI Interface */ use  and , reformat s as definitions

2010-08-04T09:51:04Z
D-Bus Connectivity UI Interface:  use <source> and <code>, reformat <div>s as definitions
Show changes

Documentation/Maemo 5 Developer Guide/Using Connectivity Components/Maemo Connectivity - Revision history

imported_>amigadave: /* Connectivity Subsystem */ convert tables to definition lists

imported_>dneary: /* Libconic Usage */

imported_>amigadave: /* Connectivity Subsystem */ add DSME link

imported_>amigadave: close list

imported_>amigadave: /* Discovering devices */ minor tidy

imported_>durazell: /* Discovering devices */

imported_>durazell: /* Bluetooth Libraries */

imported_>amigadave: use , tidy

imported_>amigadave: /* Bluetooth DBUS UI dialogs */ use

imported_>amigadave: /* D-Bus Connectivity UI Interface */ use and , reformat s as definitions

imported_>amigadave: use `, tidy`

imported_>amigadave: /* D-Bus Connectivity UI Interface */ use and `, reformat s as definitions`