D-BUS

From OLPC
Revision as of 05:14, 8 November 2007 by RafaelOrtiz (talk | contribs) (Reverted edits by 61.90.248.250 (Talk); changed back to last version by AlbertCahalan)
Jump to navigation Jump to search
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.

D-BUS is a message bus system, rather like Appletalk and DCOM, that allows applications to send messages to one another. Sugar uses D-BUS extensively, and requires that all apps interact with it via D-BUS.

The GCompris activity is a native (C language) app which uses glib to implement D-BUS ability. See dbus.c for the code.

D-BUS Services on the OLPC-XO

  • NetworkManager -- Standard Linux desktop component that provides a D-BUS API for controlling network connectivity
  • Activity DBus API -- Describes the API an activity must implement on D-BUS in order to interact with the Sugar desktop
    • 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 -- friend discovery and collaboration primitives, including a description of the Telepathy API
    • Telepathy Connection Manager
    • Telepathy StreamEngine
  • Data Store Service (Journal) -- the core data-storage operation of the laptop
  • Clipboard Service -- manages cross-activity sharing of data and files
  • Hardware Manager Service -- provides access to the OLPC-specific hardware on the laptop
  • Activity Registry Service -- registry of installed activity bundles on the laptop
  • Object Type Registry Service -- MIME-type registry service
  • Sugar Console Service

References

D-BUS website.