From 93f433a17a0aabff91a0384bf9c4f99c9cf30ae1 Mon Sep 17 00:00:00 2001 From: Richard Hult Date: Tue, 16 Mar 2004 18:00:35 +0000 Subject: 2004-03-16 Richard Hult * 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. --- doc/dbus-specification.xml | 13 +++++++++++++ 1 file changed, 13 insertions(+) (limited to 'doc/dbus-specification.xml') diff --git a/doc/dbus-specification.xml b/doc/dbus-specification.xml index 5f62cfdd..94dc740c 100644 --- a/doc/dbus-specification.xml +++ b/doc/dbus-specification.xml @@ -249,6 +249,12 @@ optimization. However, it is compliant with this specification to return the reply despite this flag. + + AUTO_ACTIVATION + 0x2 + This message automatically activates the + addressed service before the message is delivered. + @@ -674,6 +680,13 @@ However, it is also acceptable to ignore the NO_REPLY_EXPECTED flag and reply anyway. + + 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. + Mapping method calls to native APIs -- cgit