In many ways, these features are the primary motivation for developing
D-Bus; other systems would have sufficed if IPC were the only goal.
D-Bus may turn out to be useful in unanticipated applications, but
future versions of this spec and the reference implementation probably
will not incorporate features that interfere with the core use cases.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119. However, the
document could use a serious audit to be sure it makes sense to do
so. Also, they are not capitalized.
Protocol and Specification Stability
The D-Bus protocol is frozen (only compatible extensions are allowed)
as of November 8, 2006. However, this specification could still use
a fair bit of work to make interoperable reimplementation possible
without reference to the D-Bus reference implementation. Thus, this
specification is not marked 1.0. To mark it 1.0, we'd like to see someone
invest significant effort in clarifying the specification language,
and growing the specification to cover more aspects of the reference
implementation's behavior.
Until this work is complete, any attempt to reimplement D-Bus will
probably require looking at the reference implementation and/or asking
questions on the D-Bus mailing list about intended behavior. Questions
on the list are very welcome.
Nonetheless, this document should be a useful starting point and is
to our knowledge accurate, though incomplete.
Message Protocol
A message consists of a header and a body. If you think of a message
as a package, the header is the address, and the body contains the
package contents. The message delivery system uses the header
information to figure out where to send the message and how to interpret
it; the recipient interprets the body of the message.
The body of the message is made up of zero or more arguments, which
are typed values, such as an integer or a byte array.
Both header and body use the same type system and format for serializing
data. Each type of value has a wire format. Converting a value from
5星 · 超过95%的资源 需积分: 9 137 浏览量
2008-12-09
12:15:50
上传
评论
收藏 323KB PDF 举报 
评论1
最新资源