dbus/doc dbus-specification.xml, 1.15, 1.16 dbus-tutorial.xml, 1.7, 1.8

[Havoc Pennington]

Update of /cvs/dbus/dbus/doc
In directory gabe:/tmp/cvs-serv882/doc

Modified Files:
	dbus-specification.xml dbus-tutorial.xml 
Log Message:
2005-01-20  Havoc Pennington  <hp@redhat.com>

	* doc/dbus-tutorial.xml: replace > with &gt;

	* bus/services.c (bus_registry_acquire_service): validate the name
	and return a better error if it's no good.

	* doc/dbus-specification.xml: note NO_AUTO_START change

	* dbus/dbus-protocol.h (DBUS_HEADER_FLAG_NO_AUTO_START): change
	from AUTO_START, we're toggling the default

	* bus/dispatch.c: adapt the tests to change of auto-start default



Index: dbus-specification.xml
===================================================================
RCS file: /cvs/dbus/dbus/doc/dbus-specification.xml,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -d -r1.15 -r1.16
--- dbus-specification.xml	18 Jan 2005 20:42:15 -0000	1.15
+++ dbus-specification.xml	21 Jan 2005 03:44:10 -0000	1.16
@@ -757,10 +757,10 @@
                 to return the reply despite this flag.</entry>
               </row>
               <row>
-                <entry><literal>AUTO_START</literal></entry>
+                <entry><literal>NO_AUTO_START</literal></entry>
                 <entry>0x2</entry>
-                <entry>This message automatically launches an owner
-                  for the destination name before the message is delivered.
+                <entry>This message should not automatically launch an owner
+                  for the destination name.
                 </entry>
               </row>
             </tbody>
@@ -1027,8 +1027,8 @@
           flag and reply anyway.
         </para>
         <para>
-          If a message has the flag <literal>AUTO_START</literal> and the
-          destination name does not exist, then a program to own the destination
+          Unless a message has the flag <literal>NO_AUTO_START</literal>, if the
+          destination name does not exist then a program to own the destination
           name will be started before the message is delivered.  The message
           will be held until the new program is successfully started or has
           failed to start; in case of failure, an error will be returned. This

Index: dbus-tutorial.xml
===================================================================
RCS file: /cvs/dbus/dbus/doc/dbus-tutorial.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -d -r1.7 -r1.8
--- dbus-tutorial.xml	18 Jan 2005 20:42:15 -0000	1.7
+++ dbus-tutorial.xml	21 Jan 2005 03:44:10 -0000	1.8
@@ -408,7 +408,7 @@
         method call on a particular object instance, a number of 
         nested components have to be named:
         <programlisting>
-          Address -> [Bus Name] -> Path -> Interface -> Method
+          Address -&gt; [Bus Name] -&gt; Path -&gt; Interface -&gt; Method
         </programlisting>
         The bus name is in brackets to indicate that it's optional -- you only
         provide a name to route the method call to the right application
@@ -467,7 +467,7 @@
   if (connection == NULL)
     {
       g_printerr ("Failed to open connection to bus: %s\n",
-                  error->message);
+                  error-&gt;message);
       g_error_free (error);
       exit (1);
     }
@@ -490,7 +490,7 @@
                               DBUS_TYPE_INVALID))
     {
       g_printerr ("Failed to complete ListNames call: %s\n",
-                  error->message);
+                  error-&gt;message);
       g_error_free (error);
       exit (1);
     }