From da237031b3104ecdfe1f2df058179cda187fcbc8 Mon Sep 17 00:00:00 2001
From: Havoc Pennington <hp@redhat.com>
Date: Wed, 23 Apr 2003 03:36:12 +0000
Subject: 2003-04-20  Havoc Pennington  <hp@pobox.com>

	* doc/dbus-specification.sgml: document the restrictions on
	message and service names
---
 doc/dbus-specification.sgml | 19 +++++++++++++++++++
 1 file changed, 19 insertions(+)

(limited to 'doc/dbus-specification.sgml')

diff --git a/doc/dbus-specification.sgml b/doc/dbus-specification.sgml
index eda6c00e..d510ca6a 100644
--- a/doc/dbus-specification.sgml
+++ b/doc/dbus-specification.sgml
@@ -436,6 +436,25 @@
         </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">
-- 
cgit