+2003-04-20 Havoc Pennington <hp@pobox.com>
+
+ * doc/dbus-specification.sgml: document the restrictions on
+ message and service names
+
2003-04-22 Havoc Pennington <hp@redhat.com>
* dbus/dbus-message.c, dbus/dbus-marshal.c: add 64-bit integer
- if you send a message to a service then block for reply, and the service exits/crashes
after the message bus has processed your message but before the service has replied,
it would be nice if the message bus sent you an error reply.
-
- - We have a limit on the number of messages a connection can send, but
- not on how many can be buffered for a given connection.
</informaltable>
</para>
</sect2>
+
+ <sect2 id="message-protocol-names">
+ <title>Valid names</title>
+ <para>
+ Messages and services have names with type STRING, meaning that
+ they must be valid UTF-8. However, there are also some
+ additional restrictions that apply to message and service names
+ specifically:
+ <itemizedlist>
+ <listitem><para>They must contain at least one '.' (period) character</para></listitem>
+ <listitem><para>They must not begin with a '.' (period) character</para></listitem>
+ <listitem><para>They must not exceed 256 bytes in length</para></listitem>
+ <listitem><para>They must be at least 1 byte in length</para></listitem>
+ </itemizedlist>
+ As a special exception, base service names (those beginning with a colon (':') character)
+ need not contain a period.
+ </para>
+ </sect2>
+
</sect1>
<sect1 id="auth-protocol">