dbus/doc dbus-specification.xml,1.4,1.5

[Richard Hult]

Update of /cvs/dbus/dbus/doc
In directory pdx:/tmp/cvs-serv27501/doc

Modified Files:
	dbus-specification.xml 
Log Message:
2004-03-16  Richard Hult  <richard at imendio.com>

	* bus/activation.c: (bus_activation_service_created),
	(bus_activation_send_pending_auto_activation_messages),
	(bus_activation_activate_service):
	* bus/activation.h:
	* bus/dispatch.c: (bus_dispatch),
	(check_nonexistent_service_auto_activation),
	(check_service_auto_activated),
	(check_segfault_service_auto_activation),
	(check_existent_service_auto_activation), (bus_dispatch_test):
	* bus/driver.c: (bus_driver_handle_activate_service):
	* bus/services.c: (bus_registry_acquire_service):
	* dbus/dbus-message.c: (dbus_message_set_auto_activation),
	(dbus_message_get_auto_activation):
	* dbus/dbus-message.h:
	* dbus/dbus-protocol.h: Implement auto-activation.


Index: dbus-specification.xml
===================================================================
RCS file: /cvs/dbus/dbus/doc/dbus-specification.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -d -r1.4 -r1.5
--- a/dbus-specification.xml	1 Nov 2003 18:24:32 -0000	1.4
+++ b/dbus-specification.xml	16 Mar 2004 18:00:35 -0000	1.5
@@ -249,6 +249,12 @@
                 optimization. However, it is compliant with this specification
                 to return the reply despite this flag.</entry>
               </row>
+              <row>
+                <entry>AUTO_ACTIVATION</entry>
+                <entry>0x2</entry>
+                <entry>This message automatically activates the
+                addressed service before the message is delivered.</entry>
+              </row>
             </tbody>
           </tgroup>
         </informaltable>
@@ -674,6 +680,13 @@
           However, it is also acceptable to ignore the NO_REPLY_EXPECTED
           flag and reply anyway.
         </para>
+        <para>
+          If a message has the flag AUTO_ACTIVATION, then the addressed
+          service will be activated before the message is delivered, if
+          not already active. The message will be held until the service
+          is successfully activated or has failed to activate; in case
+          of failure, an activation error will be returned.
+        </para>
         <sect4 id="message-protocol-types-method-apis">
           <title>Mapping method calls to native APIs</title>
           <para>