D-BUS: Difference between revisions
Jump to navigation
Jump to search
(Add notes regarding other services on the XO) |
|||
Line 5: | Line 5: | ||
* [[NetworkManager]] |
* [[NetworkManager]] |
||
* [[Activity DBus API]] |
* [[Activity DBus API]] |
||
** Activity Service (Python implementation of the Activity DBus API) |
|||
** Activity Factory Service (Python implementation of the Activity-launching Factory DBus API) |
|||
* [[Presence Service DBus API]] Including the Telepathy API |
* [[Presence Service DBus API]] Including the Telepathy API |
||
* Telepathy Connection Manager |
** Telepathy Connection Manager |
||
* Telepathy StreamEngine |
** Telepathy StreamEngine |
||
* Clipboard Service |
* Clipboard Service |
||
* Hardware Manager Service |
* Hardware Manager Service |
Revision as of 06:24, 29 August 2007
D-BUS is a message bus system, rather like Appletalk, that allows applications to send messages to one another. The applications all run on the same CPU. If you look at the Python source code for Sugar you can see how D-BUS is being used.
D-BUS Services on the OLPC-XO
- NetworkManager
- Activity DBus API
- Activity Service (Python implementation of the Activity DBus API)
- Activity Factory Service (Python implementation of the Activity-launching Factory DBus API)
- Presence Service DBus API Including the Telepathy API
- Telepathy Connection Manager
- Telepathy StreamEngine
- Clipboard Service
- Hardware Manager Service
- Activity Registry Service
- Object Type Registry Service
- Sugar Console Service