KTp/Components/Integration Daemon: Difference between revisions
Grundleborg (talk | contribs) basic program structure outline |
Grundleborg (talk | contribs) about this component |
||
| Line 1: | Line 1: | ||
==About== | ==About== | ||
telepathy-integration-daemon is a Daemon that syncs details of your Telepathy accounts and their contacts into Nepomuk. It should always be running in the background (telepathy-monitor-kded or whatever it's called - basically a KDED module for keeping an eye on services that KDE requires to be running for fully integrated Telepathy functionality - should launch it on startup and keep it running. | |||
==Program Structure== | ==Program Structure== | ||
Revision as of 13:23, 5 February 2010
About
telepathy-integration-daemon is a Daemon that syncs details of your Telepathy accounts and their contacts into Nepomuk. It should always be running in the background (telepathy-monitor-kded or whatever it's called - basically a KDED module for keeping an eye on services that KDE requires to be running for fully integrated Telepathy functionality - should launch it on startup and keep it running.
Program Structure
TelepathyAccountMonitor
Main class TelepathyAccountMonitor monitors the Tp::AccountManager keeping track of any new accounts which are added or removed. For each existing account, creates an instance of TelepathyAccount.
TelepathyAccount
Monitors one Tp::Account. Keeps its data in sync with the relevant data in nepomuk for that account. When the account is connected, gets the contact list for the connection and creates TelepathyContact objects for each one.
TelepathyContact
Monitors one Tp::Contact. Keeps any info on it synced to Nepomuk. Destroyed when parent connection goes down.