Write about best-practices for interface names in the same place they're defined
authorSimon McVittie <simon.mcvittie@collabora.co.uk>
Tue, 17 May 2011 16:04:39 +0000 (17:04 +0100)
committerSimon McVittie <simon.mcvittie@collabora.co.uk>
Tue, 17 May 2011 16:04:39 +0000 (17:04 +0100)
commitcf32940b2ab18a760f28f1318cfbb77b7f8dff66
tree24c04497dd4f053be5f2a0b465c80df63a5a096e
parent2dd5f88cd45213733d0ae5bcda4c05a4590fb2a0
Write about best-practices for interface names in the same place they're defined

I'm deliberately using a hypothetical API from example.com, rather
than a real API, to avoid perpetuating these over-simplifications any
further than they've spread already:

- "namespaces start with org.freedesktop"
- "namespaces start with org"
- "interfaces are defined by their sole implementation"
- "services have one object implementing one interface"
- "interfaces always behave like classes"
- "interfaces are always noun phrases"
- "there is a freedesktop.org D-Bus API for screensavers"
doc/dbus-specification.xml