blob: 5d830f412f50c649db54ca4bcace7988eb0d9c23 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
|
## Overview
Mission Control—or MC for short—is a Telepathy component implementing both the [Account Manager](http://telepathy.freedesktop.org/spec/Account_Manager.html) and [Channel Dispatcher](http://telepathy.freedesktop.org/spec/Channel_Dispatcher.html) specifications. It stores your IM account settings, deals with talking to the relevant connection managers to bring accounts online where necessary, and dispatches incoming and outgoing communication channels to the relevant applications.
For example, your address book can ask Mission Control to create a call channel to bob@example.com from your Google Talk account. MC relays that request to the connection manager (Gabble) and, when the connection manager responds, passes the call channel to the application on your system which presents UI for calls (launching it if necessary).
Mission Control is licensed under the LGPL v2.1; it was originally written by Naba Kumar and Alberto Mardegan at Nokia Corporation for the Maemo platform, and is currently maintained by Collabora Ltd.
## Resources
Your favourite distribution probably already provides packages of Mission Control. Alternatively, you can obtain the source code by a variety of different means:
* [Releases (source code)](http://telepathy.freedesktop.org/releases/telepathy-mission-control)
* `git clone git://anongit.freedesktop.org/telepathy/telepathy-mission-control`
* [Git web](http://cgit.freedesktop.org/telepathy/telepathy-mission-control/)
## See also
* The other [[Components]] of the Telepathy framework.
* The [Accounts and AccountManager](http://telepathy.freedesktop.org/doc/book/chapter.accounts.html) and [Channel Dispatcher and Clients](http://telepathy.freedesktop.org/doc/book/chapter.channel-dispatcher.html) chapters of the [Telepathy Developer’s Manual](http://telepathy.freedesktop.org/doc/book/).
|
