KTp/Components/Buddy List: Difference between revisions
< KTp
Grundleborg (talk | contribs) design and reasoning, rough |
Grundleborg (talk | contribs) add link |
||
| Line 11: | Line 11: | ||
== Design == | == Design == | ||
*telepathy-integration-daemon pushes contacts into nepomuk and keeps them in sync with the servers through telepathy. It will get all contacts and their details when you initially connect to a account, and then it will (check periodically?) make sure that they stay up to date in nepomuk when they change on the server. It will also keep all contacts' presence set in nepomuk. | *[[/Real-Time_Communication_and_Collaboration/Components/Integration_Daemon|telepathy-integration-daemon]] pushes contacts into nepomuk and keeps them in sync with the servers through telepathy. It will get all contacts and their details when you initially connect to a account, and then it will (check periodically?) make sure that they stay up to date in nepomuk when they change on the server. It will also keep all contacts' presence set in nepomuk. | ||
* buddy list is populated entirely from nepomuk. it only talks to Telepathy when requesting a channel to someone (ie you double click on them to chat or something). Even presence information comes from nepomuk. Metacontacts are also implemented in Nepomuk. | * buddy list is populated entirely from nepomuk. it only talks to Telepathy when requesting a channel to someone (ie you double click on them to chat or something). Even presence information comes from nepomuk. Metacontacts are also implemented in Nepomuk. | ||
Why this way? Basically, we've tried every other possibility that we can think of (we being George and the Nepomuk folks mainly in this case) and all the other ideas fall apart at some point, whereas this one seems to be OK so far. | Why this way? Basically, we've tried every other possibility that we can think of (we being George and the Nepomuk folks mainly in this case) and all the other ideas fall apart at some point, whereas this one seems to be OK so far. | ||
Revision as of 18:52, 26 January 2010
Braindump
- use nepomuk for displaying everything.
- Nepomuk meta-contacts
Code
I (grundleborg) have some prototype code written for this, but it is not yet pushed anywhere. should push this somewhere public asap.
Design
- telepathy-integration-daemon pushes contacts into nepomuk and keeps them in sync with the servers through telepathy. It will get all contacts and their details when you initially connect to a account, and then it will (check periodically?) make sure that they stay up to date in nepomuk when they change on the server. It will also keep all contacts' presence set in nepomuk.
- buddy list is populated entirely from nepomuk. it only talks to Telepathy when requesting a channel to someone (ie you double click on them to chat or something). Even presence information comes from nepomuk. Metacontacts are also implemented in Nepomuk.
Why this way? Basically, we've tried every other possibility that we can think of (we being George and the Nepomuk folks mainly in this case) and all the other ideas fall apart at some point, whereas this one seems to be OK so far.