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

amigadave: /* telepathy-glib */ reformat table

2011-03-02T10:12:33Z

telepathy-glib: reformat table

← Older revision		Revision as of 10:12, 2 March 2011
Line 267:		Line 267:
	: LGPL		: LGPL

-	~~'''Interfaces used by libtelepathy-glib'''~~
	{\| class="wikitable"		{\| class="wikitable"
		+	\|+ Interfaces used by libtelepathy-glib
		+	\|-
	! Interface name !! License !! Dependency !! Description		! Interface name !! License !! Dependency !! Description
	\|-		\|-

amigadave: /* System decomposition view */ add contacts link

2010-10-20T12:13:20Z

System decomposition view: add contacts link

← Older revision		Revision as of 12:13, 20 October 2010
Line 13:		Line 13:
	The Telepathy framework is used to handle real time communication related signaling and abstracting all protocol dependencies to a single D-Bus interface.		The Telepathy framework is used to handle real time communication related signaling and abstracting all protocol dependencies to a single D-Bus interface.

-	Centralized addressbook is provided by the Contacts subsystem and used by the RTcom subsystem for all contact information storage and lookup purposes and it also stores transient contacts/states.	+	Centralized addressbook is provided by the [[Documentation/Maemo 5 Developer Guide/Architecture/Data Management#Contacts (Addressbook)\|Contacts subsystem]] and used by the RTcom subsystem for all contact information storage and lookup purposes and it also stores transient contacts/states.

	==RTCOM framework==		==RTCOM framework==

amigadave: /* Single-Sign-On (SSO) */ OpenID link

2010-09-02T13:55:16Z

Single-Sign-On (SSO): OpenID link

← Older revision		Revision as of 13:55, 2 September 2010
Line 357:		Line 357:
	==Single-Sign-On (SSO)==		==Single-Sign-On (SSO)==

-	SSO subsystem is a separate subsystem providing credential storage and a client library for applications. This way, user is not requested to login or enter credentials as he’s navigating between different service types within single service provider. In case of wide ticket-based system like OpenID ~~(reference)~~ , user can even use the same credential between different service providers as long as service provider accepts tickets from external providers.	+	SSO subsystem is a separate subsystem providing credential storage and a client library for applications. This way, user is not requested to login or enter credentials as he’s navigating between different service types within single service provider. In case of wide ticket-based system like [http://openid.net/ OpenID], user can even use the same credential between different service providers as long as service provider accepts tickets from external providers.

	;Purpose		;Purpose

amigadave: add maemo.org/packages links

2010-08-16T12:58:17Z

add maemo.org/packages links

← Older revision		Revision as of 12:58, 16 August 2010
Line 7:		Line 7:
	The diagram below shows the entities of the RTCOM subsystem, dependencies between them, provided interfaces and required external interfaces. The client applications are shown as packages without the fill-color. Different UI components (Messaging, Call, Log Viewer, Desktop Elements, Control Panel Applets) provide user interface layer to the system.		The diagram below shows the entities of the RTCOM subsystem, dependencies between them, provided interfaces and required external interfaces. The client applications are shown as packages without the fill-color. Different UI components (Messaging, Call, Log Viewer, Desktop Elements, Control Panel Applets) provide user interface layer to the system.

-	On intermediate layer, there’s a Mission Control package, which handle transient events and enforce system policies, providing application logic services, and libtelepathy-glib component providing GObject-style access to the Telepathy D-Bus interfaces.	+	On intermediate layer, there’s a Mission Control package, which handle transient events and enforce system policies, providing application logic services, and libtelepathy-glib component providing <code>GObject</code>-style access to the Telepathy D-Bus interfaces.

	On lowest level, there are Streaming Engine to handle actual media streaming communications, and Connection managers that abstract implementation details of different protocols to a common API. The interface is modular and platform includes Jabber (instant messaging) and SIP (voice and video calls).		On lowest level, there are Streaming Engine to handle actual media streaming communications, and Connection managers that abstract implementation details of different protocols to a common API. The interface is modular and platform includes Jabber (instant messaging) and SIP (voice and video calls).

-	The Telepathy framework is used to handle real time communication related signaling and abstracting all protocol dependencies to a single D-~~BUS~~ interface.	+	The Telepathy framework is used to handle real time communication related signaling and abstracting all protocol dependencies to a single D-Bus interface.

	Centralized addressbook is provided by the Contacts subsystem and used by the RTcom subsystem for all contact information storage and lookup purposes and it also stores transient contacts/states.		Centralized addressbook is provided by the Contacts subsystem and used by the RTcom subsystem for all contact information storage and lookup purposes and it also stores transient contacts/states.
Line 36:		Line 36:
	: libglib, libdbus, libdbus-glib		: libglib, libdbus, libdbus-glib
	;Interfaces provided		;Interfaces provided
-	: libtelepathy-glib, librtcom-telepathy-glib	+	: [http://maemo.org/packages/view/libtelepathy-glib-dev/ libtelepathy-glib], [http://maemo.org/packages/view/librtcom-telepathy-glib-dev/ librtcom-telepathy-glib]

	===telepathy-mission-control===		===telepathy-mission-control===
Line 49:		Line 49:
	: libglib, libdbus, libdbus-glib		: libglib, libdbus, libdbus-glib
	;Interfaces provided		;Interfaces provided
-	: libtelepathy-glib, librtcom-telepathy-glib	+	: [http://maemo.org/packages/view/libtelepathy-glib-dev/ libtelepathy-glib], [http://maemo.org/packages/view/librtcom-telepathy-glib-dev/ librtcom-telepathy-glib]

	===osso-mission-control===		===osso-mission-control===
Line 75:		Line 75:
	: libgtk2, libhildon1 (libhildon1, libhildonfm2, hildon-control-panel, libhildonmime, libhildonhelp), libosso-abook, libglade2, libconic, libmcclient		: libgtk2, libhildon1 (libhildon1, libhildonfm2, hildon-control-panel, libhildonmime, libhildonhelp), libosso-abook, libglade2, libconic, libmcclient
	;Interfaces provided		;Interfaces provided
-	: libaccounts, libaccounts-glade~~, libosso~~-~~rtcom-accounts~~	+	: [http://maemo.org/packages/view/libaccounts-dev/ libaccounts], [http://maemo.org/packages/view/libaccounts-glade/ libaccounts-glade]

	===rtcom-eventlogger===		===rtcom-eventlogger===
Line 88:		Line 88:
	: libglib, libsqlite3, libdbus		: libglib, libsqlite3, libdbus
	;Interfaces provided		;Interfaces provided
-	: librtcom-eventlogger	+	: [http://maemo.org/packages/view/librtcom-eventlogger-dev/ librtcom-eventlogger]

	===rtcom-eventlogger-plugins===		===rtcom-eventlogger-plugins===
Line 137:		Line 137:
	: libglib, libssl		: libglib, libssl
	;Interfaces provided		;Interfaces provided
-	: libsofia-sip-ua, libsofia-sip-ua-glib	+	: [http://maemo.org/packages/view/libsofia-sip-ua-dev/ libsofia-sip-ua], [http://maemo.org/packages/view/libsofia-sip-ua-glib-dev/ libsofia-sip-ua-glib]

	===telepathy-sofiasip===		===telepathy-sofiasip===
Line 163:		Line 163:
	: libglib, libssl, libcertman (libcst)		: libglib, libssl, libcertman (libcst)
	;Interfaces provided		;Interfaces provided
-	: libloudmouth	+	: [http://maemo.org/packages/view/libloudmouth1-dev/ libloudmouth]

	===telepathy-gabble===		===telepathy-gabble===
Line 176:		Line 176:
	: libglib, libssl		: libglib, libssl
	;Interfaces provided		;Interfaces provided
-	: libglib, libdbus, libdbus-glib, libloudmouth, libtelepathy-glib	+	: [http://maemo.org/packages/view/libglib2.0-dev/ libglib], [http://maemo.org/packages/view/libdbus-1-dev/ libdbus], [http://maemo.org/packages/view/libdbus-glib-1-dev/ libdbus-glib], [http://maemo.org/packages/view/libloudmouth1-dev/ libloudmouth], [http://maemo.org/packages/view/libtelepathy-glib-dev/ libtelepathy-glib]

	==Streaming Engines==		==Streaming Engines==
Line 215:		Line 215:
	: libglib, gstreamer (libgstreamer-plugins-base, libgstreamer-plugins-good, libgstreamer-plugins-bad), libnice, libnice-gstreamer, gupnp		: libglib, gstreamer (libgstreamer-plugins-base, libgstreamer-plugins-good, libgstreamer-plugins-bad), libnice, libnice-gstreamer, gupnp
	;Interfaces provided		;Interfaces provided
-	: libgstfarsight	+	: [http://maemo.org/packages/view/libgstfarsight0.10-dev/ libgstfarsight]

	===telepathy-farsight===		===telepathy-farsight===
Line 228:		Line 228:
	: libglib, libdbus (libdbus, libdbus-glib), libgstfarsight, libtelepathy-glib		: libglib, libdbus (libdbus, libdbus-glib), libgstfarsight, libtelepathy-glib
	;Interfaces provided		;Interfaces provided
-	: libtelepathy-farsight	+	: [http://maemo.org/packages/view/libtelepathy-farsight-dev/ libtelepathy-farsight]

	===libnice===		===libnice===
Line 241:		Line 241:
	: libglib, gstreamer (libgstreamer, libgstreamer-plugins-base)		: libglib, gstreamer (libgstreamer, libgstreamer-plugins-base)
	;Interfaces provided		;Interfaces provided
-	: libnice, libnice-gstreamer	+	: [http://maemo.org/packages/view/libnice-dev/ libnice], [http://maemo.org/packages/view/libnice-gstreamer0.10/ libnice-gstreamer]

	===telepathy-stream-engine===		===telepathy-stream-engine===
Line 271:		Line 271:
	! Interface name !! License !! Dependency !! Description		! Interface name !! License !! Dependency !! Description
	\|-		\|-
-	\|Telepathy\|\|LGPL\|\|glib, D-Bus\|\|RTCom Interface	+	\| Telepathy \|\| LGPL \|\| glib, D-Bus \|\| RTCom Interface
	\|}		\|}
-

	==Mission Control==		==Mission Control==
Line 322:		Line 321:
	: libglib, libgtk, libdbus, librtcom-eventlogger, librtcom-eventlogger-plugins, libosso, libosso-abook, libhildon1, libmcclient		: libglib, libgtk, libdbus, librtcom-eventlogger, librtcom-eventlogger-plugins, libosso, libosso-abook, libhildon1, libmcclient
	;Interfaces Provided		;Interfaces Provided
-	: librtcom-eventlogger-ui	+	: [http://maemo.org/packages/view/librtcom-eventlogger-ui-dev/ librtcom-eventlogger-ui]

	Logger is a database engine built into a library for logging all kinds of events. It’s particularly powerful for logging messages (optionally with attachments), calls and network events.		Logger is a database engine built into a library for logging all kinds of events. It’s particularly powerful for logging messages (optionally with attachments), calls and network events.
Line 376:		Line 375:
	: libglib, libxml2		: libglib, libxml2
	;Interfaces Provided		;Interfaces Provided
-	: libsignon-glib	+	: [http://maemo.org/packages/view/libsignon-glib-dev/ libsignon-glib]


Line 403:		Line 402:
	: libglib, libxml2, libcurl (libcurl3-openssl), libssl (libcrypto)		: libglib, libxml2, libcurl (libcurl3-openssl), libssl (libcrypto)
	;Interfaces Provided		;Interfaces Provided
-	: signond (ipc)	+	: [http://maemo.org/packages/view/signond-dev/ signond] (ipc)

	SSO-subsystem consists of server, here called “signond” and application libraries libsignon-glib and libsignonui. Server stores credentials in optionally encrypted database. It is running under different user id than applications. Application library accesses the storage over IPC mechanism.		SSO-subsystem consists of server, here called “signond” and application libraries libsignon-glib and libsignonui. Server stores credentials in optionally encrypted database. It is running under different user id than applications. Application library accesses the storage over IPC mechanism.
Line 409:		Line 408:
	==Protocol Stack==		==Protocol Stack==

-	Realtime communication framework connects to services using protocol plugins. Currently, XMPP/Jabber and SIP are the officially supported protocols. There’s also support for media extension of Jabber called Jingle. As described earlier, each of the protocol plugins create abstraction of some protocol to a common ~~DBUS~~ protocol.	+	Realtime communication framework connects to services using protocol plugins. Currently, XMPP/Jabber and SIP are the officially supported protocols. There’s also support for media extension of Jabber called Jingle. As described earlier, each of the protocol plugins create abstraction of some protocol to a common D-Bus protocol.

	GoogleTalk uses Jingle protocol to handle voice streaming.		GoogleTalk uses Jingle protocol to handle voice streaming.

amigadave: wikify slightly, reformat tables

2010-07-16T14:28:20Z

wikify slightly, reformat tables

Show changes

amigadave: categorise

2010-02-12T12:02:47Z

categorise

← Older revision		Revision as of 12:02, 12 February 2010
Line 443:		Line 443:
	Standard Jabber communication always goes through persistent TCP connection to the server.		Standard Jabber communication always goes through persistent TCP connection to the server.
	SIP protocol uses either UDP or TCP protocol for signaling. UDP is older and established method, while TCP is more recommended nowadays, mainly due to some particular message size and NAT traversal problems associated with UDP use. Together with SIP, standard RTP is always used for the media.		SIP protocol uses either UDP or TCP protocol for signaling. UDP is older and established method, while TCP is more recommended nowadays, mainly due to some particular message size and NAT traversal problems associated with UDP use. Together with SIP, standard RTP is always used for the media.
		+
		+	[[Category:Development]]
		+	[[Category:Documentation]]
		+	[[Category:Fremantle]]

ppessi: telepathy-ring

2010-01-27T17:15:59Z

telepathy-ring

← Older revision		Revision as of 17:15, 27 January 2010
Line 118:		Line 118:

	*Support for Skype integrated into Telepathy framework		*Support for Skype integrated into Telepathy framework
		+
		+	===telepathy-ring===
		+	{\|cellspacing="0" border="1" width="70%"
		+	\|'''Purpose'''\|\|Connection manager for cellular calls and SMS messaging
		+	\|-
		+	\|'''Source packages'''\|\|telepathy-ring
		+	\|-
		+	\|'''Licenses'''\|\|Nokia
		+	\|-
		+	\|'''Interfaces used'''\|\|libglib, libdbus, libdbus-glib, libtelepathy-glib
		+	\|-
		+	\|'''Interfaces provided'''\|\|None
		+	\|}
		+

	===sofia-sip===		===sofia-sip===
Line 175:		Line 189:
	\|'''Interfaces provided'''\|\|libglib, libdbus, libdbus-glib, libloudmouth, libtelepathy-glib		\|'''Interfaces provided'''\|\|libglib, libdbus, libdbus-glib, libloudmouth, libtelepathy-glib
	\|}		\|}
-
-

	==Streaming Engines==		==Streaming Engines==

192.100.124.218: /* Functionalities provided */

2009-10-29T12:47:50Z

Functionalities provided

← Older revision		Revision as of 12:47, 29 October 2009
Line 184:		Line 184:
	===Functionalities provided===		===Functionalities provided===

-	*Support for QoS analysis and actions, partially based on the (refreshed) implementation of RTCP support.
	*Support for fully standards compliant ICE through libnice.		*Support for fully standards compliant ICE through libnice.
	*Support for H.264		*Support for H.264
	*Support for BT HFP.		*Support for BT HFP.
	*Support for Skype in Telepathy framework.		*Support for Skype in Telepathy framework.
-

	===gst-plugins-farsight===		===gst-plugins-farsight===

78.105.109.196: typo

2009-10-28T11:29:11Z

typo

← Older revision		Revision as of 11:29, 28 October 2009
Line 20:		Line 20:
	*Support for comprehensive logging		*Support for comprehensive logging
	*SSO related components		*SSO related components
-	*~~Suport~~ for heartbeat	+	*Support for heartbeat
	*Device presence profiles		*Device presence profiles
	*Support for BT HFP		*Support for BT HFP

78.105.109.196: fix copy-paster errors in farsight2 section

2009-10-28T11:27:24Z

fix copy-paster errors in farsight2 section

← Older revision		Revision as of 11:27, 28 October 2009
Line 209:		Line 209:
	\|'''Purpose'''\|\|The Farsight project is an effort to create a framework to deal with all known audio/video conferencing protocols. On one side it offers a generic API that makes it possible to write plugins for different streaming protocols, on the other side it offers an API for clients to use those plugins. This package provides the core Farsight 2 library.		\|'''Purpose'''\|\|The Farsight project is an effort to create a framework to deal with all known audio/video conferencing protocols. On one side it offers a generic API that makes it possible to write plugins for different streaming protocols, on the other side it offers an API for clients to use those plugins. This package provides the core Farsight 2 library.
	\|-		\|-
-	\|'''Source packages'''\|\|~~loudmouth~~	+	\|'''Source packages'''\|\|farsight2
	\|-		\|-
	\|'''Licenses'''\|\|LGPL		\|'''Licenses'''\|\|LGPL
Line 215:		Line 215:
	\|'''Interfaces used'''\|\|libglib, gstreamer (libgstreamer-plugins-base, libgstreamer-plugins-good, libgstreamer-plugins-bad), libnice, libnice-gstreamer, gupnp		\|'''Interfaces used'''\|\|libglib, gstreamer (libgstreamer-plugins-base, libgstreamer-plugins-good, libgstreamer-plugins-bad), libnice, libnice-gstreamer, gupnp
	\|-		\|-
-	\|'''Interfaces provided'''\|\|~~libgstfaright~~	+	\|'''Interfaces provided'''\|\|libgstfarsight
	\|}		\|}
-

	===telepathy-farsight===		===telepathy-farsight===