summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorSimon McVittie <simon.mcvittie@collabora.co.uk>2007-09-27 14:03:53 +0000
committerSimon McVittie <simon.mcvittie@collabora.co.uk>2007-09-27 14:03:53 +0000
commitfb583063f80eb5dd7ccbd3ea206bddc3a0fd7368 (patch)
tree8007757614c51f1aeaa7cfc68e369080d2bad9b7
parentf25ec0e6e124c574cb0eb01f940d2b285aa1e6e5 (diff)
Explain the desired semantics for chatroom and 1-1 D-Bus tubes
-rw-r--r--spec/Channel_Type_Tubes.xml15
1 files changed, 15 insertions, 0 deletions
diff --git a/spec/Channel_Type_Tubes.xml b/spec/Channel_Type_Tubes.xml
index b66ae980..c7a2c24e 100644
--- a/spec/Channel_Type_Tubes.xml
+++ b/spec/Channel_Type_Tubes.xml
@@ -54,6 +54,21 @@ Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
objects/interfaces that would be exported by a service of that name
on a bus, or all participants are expected to export those
objects/interfaces.</p>
+
+ <p>In a multi-user context (Handle_Type_Room) the tube behaves
+ like the D-Bus bus daemon, so participants can send each other
+ private messages, or can send broadcast messages which are
+ received by everyone in the tube (including themselves).
+ Each participant has a D-Bus unique name; connection managers
+ must prevent participants from sending messages with the wrong
+ sender unique name, and should attempt to avoid participants
+ receiving messages not intended for them.</p>
+
+ <p>In a 1-1 context (Handle_Type_Contact) the tube behaves like
+ a peer-to-peer D-Bus connection - arbitrary D-Bus messages with
+ any sender and/or destination can be sent by each participant,
+ and each participant receives all messages sent by the other
+ participant.</p>
</tp:docstring>
</tp:enumvalue>