diff options
| author | Anders Carlsson <andersca@codefactory.se> | 2003-03-26 21:06:17 +0000 |
|---|---|---|
| committer | Anders Carlsson <andersca@codefactory.se> | 2003-03-26 21:06:17 +0000 |
| commit | 24ae27fa7690dd57f17236d0bb51993fc4c9bd70 (patch) | |
| tree | 49238d6d72a81e686215eac2a380be3c24e71e0d | |
| parent | b01a215f54143f6ad6b83d435ac738ef79b58752 (diff) | |
2003-03-26 Anders Carlsson <andersca@codefactory.se>
* doc/TODO:
Add note about automatic service activation.
* doc/dbus-specification.sgml:
Rename the specification and clarify a few things.
| -rw-r--r-- | ChangeLog | 8 | ||||
| -rw-r--r-- | doc/TODO | 2 | ||||
| -rw-r--r-- | doc/dbus-specification.sgml | 32 |
3 files changed, 27 insertions, 15 deletions
@@ -1,5 +1,13 @@ 2003-03-26 Anders Carlsson <andersca@codefactory.se> + * doc/TODO: + Add note about automatic service activation. + + * doc/dbus-specification.sgml: + Rename the specification and clarify a few things. + +2003-03-26 Anders Carlsson <andersca@codefactory.se> + * Doxyfile.in: * dbus/dbus-address.c: * dbus/dbus-dict.c: @@ -37,5 +37,5 @@ - Implement all the needed resource limits to keep clients from killing the message bus. - + - Automatic service activation, should probably be done through a message flag. diff --git a/doc/dbus-specification.sgml b/doc/dbus-specification.sgml index da1d07a1..476d0afe 100644 --- a/doc/dbus-specification.sgml +++ b/doc/dbus-specification.sgml @@ -2,9 +2,9 @@ ]> <article id="index"> <artheader> - <title>D-BUS Protocol Specification</title> - <releaseinfo>Version 0.4</releaseinfo> - <date>17 February 2003</date> + <title>D-BUS Specification</title> + <releaseinfo>Version 0.7</releaseinfo> + <date>26 March 2003</date> <authorgroup> <author> <firstname>Havoc</firstname> @@ -422,10 +422,11 @@ <sect1 id="auth-protocol"> <title>Authentication Protocol</title> <para> - Before the flow of messages begins, two applications - must authenticate. A simple text protocol is used - for authentication; this protocol is a SASL profile, - and maps fairly directly from the SASL specification. + Before the flow of messages begins, two applications must + authenticate. A simple plain-text protocol is used for + authentication; this protocol is a SASL profile, and maps fairly + directly from the SASL specification. The message encoding is + NOT used here, only plain text messages. </para> <para> In examples, "C:" and "S:" indicate lines sent by the client and @@ -1309,13 +1310,16 @@ </informaltable> </para> <para> - Before an application is able to send messages to other applications it - must send the <literal>org.freedesktop.DBus.Hello</literal> - message to the message bus service. If an application tries to send - a message to another application, or a message to the message bus - service that isn't the - <literal>org.freedesktop.DBus.Hello</literal> message, it will - be disconnected from the bus. + Before an application is able to send messages to other + applications it must send the + <literal>org.freedesktop.DBus.Hello</literal> message to the + message bus service. If an application tries to send a + message to another application, or a message to the message + bus service that isn't the + <literal>org.freedesktop.DBus.Hello</literal> message, it + will be disconnected from the bus. If a client wishes to + disconnect from the bus, it just has to disconnect from the + transport used. No de-registration message is necessary. </para> <para> The reply message contains the name of the application's base service. |